GitHub now gives free users unlimited private repositories

GitHub is by far the most popular way to build and share software. That said, one weakness of the platform is that it limits who can create private repositories – that is, software projects that aren’t visible to the broader public, and are shared only with a handful of pre-defined collaborators – to paying users.

New year, new upgrades.

Introducing unlimited free private repositories, and a new unified Enterprise product.https://t.co/6YB1BynM4A pic.twitter.com/0EXJO8MqEu

— GitHub (@github) January 7, 2019

Fortunately, that’s no longer the case, as GitHub today announced it was giving users of its free plan access to unlimited private repositories. This is great news for GitHub’s users, but there is a caveat, of course.

Private repositories on free accounts are limited to three collaborators apiece. So, while this might work for a small project (like, for example, a team competing in a hackathon), it isn’t particularly well-suited for actual commercial usage.

That was probably a deliberate move from GitHub. There’s little risk of the company cannibalizing its existing paid users with this new free offering.

The 💜 of EU tech

The latest rumblings from the EU tech scene, a story from our wise ol' founder Boris, and some questionable AI art. It's free, every week, in your inbox. Sign up now!

Until recently, developers who wanted to create private git repositories without opening their wallets were forced to use a rival service – most frequently BitBucket. Today’s news, obviously, isn’t great for Atlassian’s flagship code sharing platform, but it does mean that coders aren’t forced to use two disparate code management services for their private and public projects

I also wonder what ubiquitous private repositories will mean for Github’s culture of self-exhibition and sharing.

The absence of free private repositories essentially meant that people were forced to air their dirty laundry – their half-baked projects that never got finished and the clumsy spaghetti code they’d sooner forget. Now that people have the option to hide this behind a perfect shroud, will this harm GitHub’s culture of shameless openness and candidness?

Maybe. Time will tell.