Hacker News Reader

Comment by oefrha | Hacker News Reader

First of all, thank you, this is great news.

That said, the news made me wonder what exactly I’m still paying for with my personal Pro account. I went to the pricing page https://github.com/pricing and it seems Pro isn’t even listed anymore? And the Billings page https://github.com/settings/billing says “Pages, Wikis, protected branches and more for Pro developers” without any further explanation or link to docs explaining the differences. I can only assume that Pro has the same set of features as the $4/user/mo Team plan, but the messaging is certainly pretty confusing, don’t you think?

(I sure hope this isn’t a sign of neglect for individual developers, who are still the backbone of open source activities.)

View on HN

I still get a Pro option when going to https://github.com/account/upgrade from a free account, and it seems to match Teams, here's the blurb:

> Required reviewers in private repos

> Protected branches in private repos

> Repository insights in private repos

> Wikis in private repos

> Pages in private repos

> Code owners in private repos

> 3,000 minutes for GitHub Actions

> 2GB of storage for packages

So basically Pro and Team are the same now?

Edit: The FAQ points to Github product page [1] which list GitHub Team having 10K Actions instead.

[1] https://help.github.com/en/github/getting-started-with-githu...

So... wouldn't this mean GitHub Team with a single user is better than GitHub pro?

Now that's just weird, pricing page says 3k for Team.

Thanks for the confirmation, that’s what I figured. It would be nice to see this laid out somewhere public, preferably the pricing page, not gated behind a free account.

It's on the FAQ at the bottom of the announcement blog: https://help.github.com/en/github/getting-started-with-githu...

Though it does require a bit of between the line reading

I think it's Okay. If you are going with the Pro account today you need a particular feature. So you likely know what you are looking for.

I went to go downgrade to the free plan and noticed that GitHub Pages static sites served from Private repos still require payment. That will keep me on $4/month for now.

I'm curious: since GitHub Pages intended to PUBLISH pages, why to make the repo PRIVATE?

Sometimes people want to keep the code, commits, etc. private but maintain a blog

Use a private repo, attach a code action to publish your output of your favourite blog to static html output to a public GitHub pages repo.

Nobody's saying it's not possible with a hack or workaround, just that it doesn't work out of the box.

Reply on news.ycombinator.com