[caseymarquis]

Given git's distributed nature, I can't imagine either service going down for a day could have that enormous of an impact. I'd be curious to know how people manage that. I would think other services which point to git.* would largely have some option for a manual work around, or would not be utilized in mission critical roles.

[edejong]

But git is not truly distributed. Each 'node' in the network does not automatically gets access to new trusted nodes (remotes). Management of the distributed nature is still manual, meaning that your CI/CD system cannot suddenly pull changes from your local developer machine, instead of GitHub/GitLab/Gerrit/...

In an ideal world, each commit is cryptographically signed and automatically distributed to a large number of nodes. Only correctly signed commits would be picked up by CI/CD and the build artifacts would use the digital signature of the code to further deploy the resources in a trustworthy manner.

[manigandham]

Its mostly about the project management, issue tracking, pull requests, CI/CD, releases and other features being unavailable. Not the source code itself.

[pgt]

Continuous integration is typically not distributed, and it blocks releases.