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?
Introducing unlimited private repositories
41–50 of 662 posts
Re: Introducing unlimited private repositories
#42That's cool but seeing as Bitbucket has unlimited private repos for everyone, I'll be sticking with Bitbucket for private trash and Github for public trash.
GitLab too.
Re: Introducing unlimited private repositories
#43This is, of course, a positive way to spin the fact that they're raising prices significantly for many organizations. I'm glad there's at least a year that we can keep using the old plans.
[deleted]
Re: Introducing unlimited private repositories
#44For comparison, quoting from the AWS CodeCommit pricing page... AWS CodeCommit costs: $1 per active user per month For every active user, your account receives for that month: 10 GB-month of storage 2,000 Git requests And the 1 year free tier is: 5 active users 50 GB-month of storage 10,000 Git requests
It took a bit of searching to find out what a "Git Request" entailed: "A Git request includes any push or pull that transmits repository objects. The request does not count towards your Git request allowance if there is no object transfer due to local and remote branches being up-to-date."
Anyone who's using CodeCommit - have you hit the limits? How much did you go over by?
Re: Introducing unlimited private repositories
#45Pretty 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?
Why don't you just add the SSH public keys of your CI machine to your own GitHub account?
I wouldn't want a CI to store a key that has R/W access to all my repos in all my organizations. I'm in at least 5 active organizations that I would be putting at risk
Re: Introducing unlimited private repositories
#46Its unfortunate that this doesn't promote trying to get business users to look at the code. In our organization 3 or 4 users are read only and really just go in at times to check specific errors, or logic for certain SQL queries, they don't really contribute. We will now have to pay $9 per month for these type of "read only" users.
Couldn't you use some other kind of display for these users? Seems like you'd only need 2 or 3 of these to justify a small project to get them the information they need without needing to be a paying GitHub user.
Re: Introducing unlimited private repositories
#47Do outside collaborators count as paid users?
[deleted]
Re: Introducing unlimited private repositories
#48I'm glad. Occasionally I would delete abandoned projects to make space and now they can live forever to remind me of my failure!
[deleted]
Re: Introducing unlimited private repositories
#49The main image on that page looks remarkably similar to the 2010 Visual Studio logo:
http://blogs.msdn.com/b/samer/archive/2010/01/27/quick-share...
Re: Introducing unlimited private repositories
#50Its unfortunate that this doesn't promote trying to get business users to look at the code. In our organization 3 or 4 users are read only and really just go in at times to check specific errors, or logic for certain SQL queries, they don't really contribute. We will now have to pay $9 per month for these type of "read only" users.
Couldn't you just use the same account for all of them, with a shared password?