A git remote you already control, already synced, and ready before the outage — not something you can set up mid-incident, since creating it requires reaching GitHub in the first place. Check live GitHub status first if you're wondering right now.
GitHub serves millions of repositories from one shared platform. An incident on their side affects every account at the same time, and there's nothing an individual team can do to speed up GitHub's own recovery — you're waiting on someone else's infrastructure, on someone else's timeline.
git clone --mirror https://github.com/you/your-repo.git cd your-repo.git git push --mirror https://rithub.dev/you/your-repo.git
That's the entire one-time setup. From then on, a quick git fetch / mirror re-push keeps the Rithub copy current, and during any future GitHub outage your team pushes and pulls against the remote that's actually reachable:
git remote add rithub https://rithub.dev/you/your-repo.git git push rithub main git pull rithub main
| Moves with a mirror push | Needs separate handling |
|---|---|
| Full commit history, every branch, every tag | Open issues and pull request threads |
| Git objects and refs exactly as they exist on GitHub | GitHub Actions run history |
For the issue/PR side specifically, see migrating GitHub issues and pull requests.
Switching from one third-party host to another just swaps which company's outage you're exposed to next. A self-hosted git server like Rithub only goes down if your own server does — infrastructure you control directly, not a dependency on a second company's uptime.
Sign up freeImport from GitHub