It's a hassle, for sure. If this incident cost you time, I would advocate for you to invest a brief amount of time to hedge against GH. The next downtime may not be as brief.
These steps will cost you < 15 minutes but you could end up with significant savings.
1. make an account on gitlab
2. create a new repo
3. configure it to mirror your existing GH repo. The mirror will periodically pull from GH without any interaction from you, so you always have another option.
To be clear, I don't have any opinions about the operations of Github vs Gitlab. I have no idea which has superior procedures or equipment to avoid downtime. But I am sure that this small effort to diversify is worthwhile.
EDIT: wowsers downvotes for practical advice? Downvoters, please chime in on how my advice could be improved.
How will this save you from outages like this one?
The problem is usually not that people loose access to their code (you usually have a local cache), it's that you can't open or review PRs, and that you can't trigger CI builds.
Using _both_ GitHub and GitLab simultaniously for more advanced workflows is a big hassle.
These steps will cost you < 15 minutes but you could end up with significant savings.
1. make an account on gitlab
2. create a new repo
3. configure it to mirror your existing GH repo. The mirror will periodically pull from GH without any interaction from you, so you always have another option.
To be clear, I don't have any opinions about the operations of Github vs Gitlab. I have no idea which has superior procedures or equipment to avoid downtime. But I am sure that this small effort to diversify is worthwhile.
EDIT: wowsers downvotes for practical advice? Downvoters, please chime in on how my advice could be improved.