Every time there's an outage with $SCMProvider, there's always a comment like this.
Git is not GitHub. GitHub is not git.
You can absolutely do git in a distributed way.
That doesn't help when your business workflow relies on GitHub for access control, artifact hosting, issue management, PR coordination & approval, and all the thousand other things that people use GitHub for.
I mean... it still is? I can work on my codebase and commit on my local machine. Push remote to Gitlab if Github is down. When Github is back up I can push to Github. What's the problem?
To answer most comments here, of course git is still decentralized, it’s just that almost no one use it like that. We chose the easier route, as usual. Just like most people don’t host their texts and photos on their own site.
Note that your repo stays usable even while GitHub is down, and your team can sync their work afterwards. Or if you prefer, you can switch to a different remote without much trouble.
On a different note, I do host my own Git server, but between maintainance downtime, power outages and ISP issues, my availability isn't nearly as good as GitHub's.
Git is not GitHub. GitHub is not git.
You can absolutely do git in a distributed way.
That doesn't help when your business workflow relies on GitHub for access control, artifact hosting, issue management, PR coordination & approval, and all the thousand other things that people use GitHub for.