If your GitHub account was flagged or suspended, your code is not gone — any local clone on your machine, a teammate's machine, or a CI runner already has the full history. Push that clone to a new remote and you are back to working in minutes, while you separately appeal the suspension.
Check, in this order:
git clone in.A single working clone is enough — .git inside it holds every commit, branch, and tag, independent of whether GitHub still serves the hosted copy.
Create an account on a code host you do not depend on a single company's suspension policy for — for example Rithub, our own self-hosted instance:
git remote add rithub https://git.ereboslab.com/<you>/<repo>.git git push rithub --mirror
--mirror pushes every branch and tag in one command, not just the branch you have checked out.
git log --oneline -10 # compare against what you remember git branch -a # confirm every branch pushed git tag # confirm every tag pushed
File or continue GitHub's support appeal for the suspended account. This is independent of Step 1–3 — you do not need to wait for the appeal to resolve before your team is working again on the new remote.
git remote set-url origin <new-url> on every machine and CI config once the new host is confirmed working.Can I still get my code if the account is flagged?
Usually yes — any local clone already has your full history; you only need a working git push to a new remote.
What if no local clone exists anywhere?
Check every machine, CI runner, and teammate first; GitHub's own support-appeal flow is the only path if truly none exists.
Does moving off GitHub mean giving up the appeal?
No — do both. Keep the appeal open and get a working copy live elsewhere immediately.
Do issues and pull requests move too?
Git history moves with a normal push. Issues/PR threads are separate metadata and need their own export if the account is still reachable.
Need an account fast? Email [email protected].