"Prevention is ideal, but detection is a must"

It’s amazing how this is accepted in the software world. Move fast and break things, such a different philosophy to other areas.

"I will not be harassed in my own private domicile"

-- Jesse Pinkman

Yes, git is.

The issues, comments, PRs, wikis etc... that we all came to depend on aren't.

Git is, but the APIs and all the services they provide around it aren't.

That said, I think it's a bit weird that they don't store the data of the services around the code itself in git, like they do with e.g. sites. That way you'd have an `issues` branch that you could still access if github is down.

But that would probably pave the way for easy migrations away from Github.

Every project i have been on where we built for availability and resilience has inevitably had at least one single point of failure. Usually it is something deemed non critical, but somehow can still bring the infrastructure down (A single DNS server at one of our production sites did this, we have 2 more accessible via a VPN tunnel, it was deemed if the production DNS went down the other two were still reachable, to bad the day it happened the tunnel was down too).

Also you have to deal with sysadmin error, i know us sysadmins are practically perfect in every way, but occasionally we make mistakes....big mistakes. ;)

So redirecting might not always be possible.....

Durability isn't uptime.