[shizzy0]

I was a paying GitHub customer, but they had such a crummy private repo policy at the time (I think only 5 private repos were allowed) it forced me to make poor technical decisions: "I'll delete this github repo, keep my local copy, to open up a slot." I switched all my private repos to gitlab and stopped paying for github and was happier for it.

Later github changed its policy to something saner, but I never switched back to using github for private repos. This decision by gitlab even if it's rescinded, however, might give me the impetus to do so.

[benjymo]

I'm doing the same for the 5 user limit on GitLab currently.

But the pricing is just too steep for me to justify setting up, e.g. an extra user for some automated tasks.

[will-bradley]

You shouldn't need a user account for automated tasks, that's what webhooks and deploy keys are for.

[clintonb]

I don’t know if this issue has been resolved, but as late as four years ago, GitLab didn’t have a notion of a service user. If you wanted a server to authenticate and pull from a private repo, you had to use a licensed account to do so. This meant your 5 user tier became a 4 user tier.

[voffk]

Project access tokens (https://docs.gitlab.com/ee/user/project/settings/project_acc...) is what you need and they have been around for 2+ years

[pooper]

I had forgotten why I default every little hello world type repo I create on GitHub to public. I knew there was a reason I started doing that but had forgotten.

The five slots were precious and I didn't want to waste them.

[L6489afSMNLNFDa]

Which, of course, was entirely their goal: to get more public content to increase the network effect.