[sidstling]

In my experience git is excellent at being offline. I’m not sure if we would have had problem if our team foundation setup had ever went off line, but we moved to git long ago because it’s what every single IT-based student learns in my country. With every potential hire knowing git and almost none of them knowing tfd/vsts, it seemed silly not to migrate since the platforms both work well for what we need and git was cheaper over all.

You can use git outside of GitHub and Microsoft though, I mean, you could always use bitbucket.

[greglindahl]

In my experience, most companies that use "github" (and not "git") cannot get much done if github is down.

[setquk]

So much this. All the pipeline and delivery stuff is glued into github’s API. Most companies aren’t using git any more but github and git is just a dependency. I’ve even seen developers who are unaware that git can exist without github.

I incidentally think this is a completely terrible outcome.

[daveFNbuck]

It doesn't really mater what service provider you use. You can't do anything that requires a sync if the server is down. You can do a bit of local development, but things like automated tests and deployment to staging servers will tend to break if they can't access the source.

[TeMPOraL]

Or badly configured CI, that redownloads dependencies all the time instead of caching them locally.