Live data from Hacker News

Introducing unlimited private repositories

github.com

101–110 of 662 posts

Re: Introducing unlimited private repositories

#101

Hmm, I still will use Gitlab instead of Github. Unlimited public and private repos for free is nice.

Does anyone know how Gitlab plan to sustain that?

I believe that their profit comes from selling the Enterprise Edition of GitLab and support. gitlab.com and the Community Edition are all free, and I believe they intend to keep it this way.

Re: Introducing unlimited private repositories

#102

I'm sure a lot of people will be moving from Bitbucket to this, Bitbucket's plans were great for hundreds of repos, but Github's ecosystem is definitely preferable.

I'm not sure, Bitbucket's price effectively is $1/user and Github's $9/user. I wouldn't expect organisations to move to Bitbucket either, as change is generally costly in terms of man-hour, but current price structure makes Bitbucket eight-fold cheaper.

[deleted]

Re: Introducing unlimited private repositories

#103
Now I have to pay for external collaborators? Are you kidding me? We are a small team of 5, but making softwares for other, I'll have to move away from github with the new pricing, we have nearly ten people per repository that might just be exec who never accessed the repo but must have access to it.

Re: Introducing unlimited private repositories

#105
post #40

A small comparison: Team | Cost Before | Cost Now 1 repo, 5 users | $25 | $25 1 repo, 10 users | $25 | $70 11 repos, 5 users | $50 | $25 11 repos, 10 users | $50 | $70 5 repos, 50 users | $25 | $430 50 repos, 5 users | $100 | $25 50 repos, 50 users | $100 | $430 I'm not sure how common are organizations with few users and large number of repose - I guess software houses that keep old projects (for maintenance and fut…

We have a tons of repositories, most are currently on BItbucket, because GitHub was to expensive. Only our largest projects are on GitHub. Our team is maybe 8 developers, depending on consultants, interns and other temporary employments, but we have 20 - 30 repos. I think for small companies that do all development in-house, having large number of repos, and few developer is a pretty normal. The way I look at it, Git…

Except that now GitHub is 9x more expensive than BitBucket (and for a team under 5 developers, GitHub is $25 vs. BitBucket's $0).

Re: Introducing unlimited private repositories

#106
post #40

A small comparison: Team | Cost Before | Cost Now 1 repo, 5 users | $25 | $25 1 repo, 10 users | $25 | $70 11 repos, 5 users | $50 | $25 11 repos, 10 users | $50 | $70 5 repos, 50 users | $25 | $430 50 repos, 5 users | $100 | $25 50 repos, 50 users | $100 | $430 I'm not sure how common are organizations with few users and large number of repose - I guess software houses that keep old projects (for maintenance and fut…

At least in our case the new pricing would be couple % below what we used to pay under the per-repo pricing scheme. And about 30% less if we merge our two organizations.

Re: Introducing unlimited private repositories

#107
post #96

I'm sure a lot of people will be moving from Bitbucket to this, Bitbucket's plans were great for hundreds of repos, but Github's ecosystem is definitely preferable.

Why? BitBucket is superior in every respect, plus importantly they give free private repos for every user. No price gouging like we're seeing with GitHub.

Oh, come on. It's OK to dislike this change, but "BitBucket is superior in every respect" and "price gouging" are far from objectively obvious.

Re: Introducing unlimited private repositories

#108
post #21

Pretty angry that Github have made this change with no mechanism for adding machine users without paying a per month charge. It seems like a key feature, which is currently horribly painful to manage and now expensive. How does everyone else create credentials that CI can use to checkout code?

Both Travis and Circle automatically install a deploy key into the project. It doesn't require additional machine users.

That's fine if you have a single repo, but CI normally needs to access lots of different repos. GitHub's documentation describes why you need machine users for anything but the most trivial deployment.

https://developer.github.com/guides/managing-deploy-keys/

It's also what GitHub does internally.

Re: Introducing unlimited private repositories

#109
post #29
post #21

Pretty angry that Github have made this change with no mechanism for adding machine users without paying a per month charge. It seems like a key feature, which is currently horribly painful to manage and now expensive. How does everyone else create credentials that CI can use to checkout code?

Deploy keys

https://developer.github.com/guides/managing-deploy-keys/

Re: Introducing unlimited private repositories

#110
So what makes them think that they can get away with it? There's already decent competitors - GitLab, BitBucket, Azure or you can just host your own git repos - gitlab will even give you a nice Web UI for it. Why do they think that people with stick with github, if we're talking $thousands/year then surely migrating to another git repo provider is worth it?
Post reply on HN