zlacker

What are folks using to isolate themselves from these sorts of issues? Adding a cache for any read operations seems wise (and it also improves perf). Anyone successfully avoid impact and want to share?

>>8organ+(OP)
Coffee break.

>>8organ+(OP)
Use the local clone that I already have, given that `git` was always intended to be usable offline.

>>8organ+(OP)
Previous job had a locally hosted Github Enterprise and I was always resentful when everybody else on Twitter was like "github down! going home early!". :(

Of course it still sucked when some tool decided I needed to update dependencies which all lived on regular Github, but at least our deployment stuff etc still worked.

>>8organ+(OP)
In a previous life, for one org's "GitOps" setup, we mirrored Gitlab onto AWS CodeCommit (we were an AWS shop) and used that as the SoT for automation.

That decision proved wise many times. I don't remember CodeCommit ever having any notable problems.

That said: if you're using GitHub in your actual dev processes (i.e. using it as a forge: using the issue tracker, PRs for reviews, etc), there's really no good way to isolate yourself as far as I know.

>>ben0x5+dh
DNS overrides during failure times and cloning those repos in GH Enterprise would be next logical next step I guess

>>Karell+w9
Yep. I've been using my git server to mirror any and all software that I find slightly interesting. Instead of starring repos, I make them available when GitHub goes down :D