I really don't understand this fear about a single pillar of failure, as people were in tears about the Ghostty thread yesterday. git is not GitHub. git is not HTTP. git is inherently decentralized with no concept of client/server. In git there is only local and a plurality of remotes. That said the solution is simple. Open a secondary, or a new primary, account with another provider and add it to your project's list…
> Boom, problem solved Not if your CI depends on github, or if you have specific actions to review things, or if you use SSO because you're an enterprise, or.... Workarounds exist for each of these cases, but they add significant friction. That's not terrible if you're one person, but if you're an org? big problem.
Enterprise Cloud up time is 100% for last 90 days for most services, with a one being at 99.98 and one at 99.97.
Enterprise customers get an SLA