[7777fps]

GitHub has significant vendor lock-in, so it makes sense to make it free to capture the market before a competitor gets traction.

[Speculation:]

Perhaps they've run the numbers and can figure out that they make enough money from enterprise clients and will make enough more money from the 'marketplace' being a channel for selling github integrations and addons to cover this cost of not trying to monetize through supporting teams.

It also moves a large base from 'customer' with needed support to free users which don't need the same level of support.

[fileeditview]

What exactly is the lock-in mechanism?

E.g. I have git repos where I use multiple remotes (1 Github, 2 Gitlab..). So git is the same as everwhere.. I never felt locked in. It's not too hard to transfer your repos to another provider.

[7777fps]

GitHub is not git.

GitHub has pull requests, actions (mini CI integrations), other fuller integrations running off github hooks.

It's the issues, and pull requests that are the most immediate lock in. Transfer away and you lose your issues and PR history.

But more deeply it's the integrations. Even if it's all theoretically possible through other providers, if you have a working CI system set up to "just work" through GitHub then there's little chance you'll want to migrate to a different provider and have to re-do all that configuration.

Even with a dedicated dev-ops team it's weeks of disruption, not to mention the possibility to get half way through and discover something doesn't work the same way in [Competitor].

If you're up and running with github PRs driving JIRA issues and JIRA issues feeding into GitHub issues. And you have paid github marketplace integrations delivering value, then you're not going to look at a competitor unless that competitor is offering something that GitHub doesn't do.

Up to now the competitors have only differentiated on price as far as I can tell. There's certainly no killer feature of GitLab that people talk about.

[dehrmann]

> GitHub has significant vendor lock-in

Do they? Unless you're on GitHub Enterprise, migrating is just moving your repos over the weekend, setting up new webhooks, emailing everyone a command to switch their upstream URL, and hoping the new workflow works for you. For teams of <100, this it one of the easier transitions to make.

[bdcravens]

There are external services that integrate with Github but not Gitlab. (though more and more are also adding Gitlab integration)

[aledalgrande]

How are you gonna migrate issues and actions?

[gbear605]

I'm not sure about actions, but GitLab[1] and BitBucket[2] have the ability to import issues.

[1]: https://docs.gitlab.com/ee/user/project/import/github.html

[2]: https://confluence.atlassian.com/get-started-with-bitbucket/...

[samanthalee233]

Thanks for sharing this, I'm a GitLab community advocate, and wanted to see if you'd like to join our #GitChallenge - You share a review of GitLab vs GitHub (whether positive/negative/neutral), and we send you some swag. More info if you're interested: https://about.gitlab.com/blog/2020/04/14/github-free-for-tea...

[vincnetas]

Exaclty this. On gitlab you can run your CI runners on anything you like. Basically start docker and forget. Curious how github actions compare.

Update: apperantly github also has self hosted runners

https://help.github.com/en/actions/hosting-your-own-runners/...