Quick answer: Maintain an automated mirror of the repository on a second host so a primary outage does not block the team and the history is backed up.
If your one Git host goes down, so does your whole team. A mirror removes that single point of failure. Here is how.
How to fix it
1. Set up a mirror remote
Configure a second host as a mirror of the repository including all branches and tags.
2. Sync automatically
Push to the mirror on a schedule or via CI so it stays current without manual effort.
3. Practice the failover
Verify the team can switch to the mirror so it actually works when you need it.
Catching the ones you can't reproduce
The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.
Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.
This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.
Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.