Best practice for me is to hope this happens on Friday afternoon and then take a half day... so all according to plan!

I just want to be able to run self-hosted CI without it failing due to github

I don't understand. Almost all of GitHub is a centralized service, while the self-hosted version is available to a select few enterprise partners.

What's the roadblock on doing self-hosted CI without failing due to GitHub? It would be as simple as not using GitHub I think

If you're already using a cloud provider, they [1] all [2] have [3] private git repo services.

You can set up a cronjob to sync them, or some have built-in config to do the mirroring [4].

I used Google's mirroring option before. It was fine, but we never had to use it (local copies were sufficient when GH was slow one day).

[1] https://cloud.google.com/source-repositories

[2] https://aws.amazon.com/codecommit/

[3] https://azure.microsoft.com/en-us/services/devops/repos/

[4] https://cloud.google.com/source-repositories/docs/mirroring-...

We don`t need to forget about small but better providers, like DNS made easy or it`s younger brother Constellix I also read one guy at webhosting talk. he said DNS simple have some new good features

GitHub better use something more trusted. AWS outages is so well known :/

You could have a selfhosted gitea or gitlab instance that mirrors your GitHub repo. I use that as backup for some GitHub repos.

Self host GitLab seems like a good approach here.

We use a cluster of self-hosted GitLab instances. Their update cadence has been on a roll and their development process is much more transparent compared to GitHub imo because it's a lot easier to see how they comment and discuss when they have "all-remote" baked into the core of their workflow

Believe it or not, we have higher service availability hosting GitLab ourselves than GitHub