A plain git push --mirror only moves commits, branches, and tags — issues and pull requests live in GitHub's database, not in git itself. Bringing them over needs a migration tool that talks to GitHub's API, not just git.
Moves with git push --mirror: commits, branches, tags, git objects Does NOT move: issues, PR threads/comments, labels, milestones, Actions run history
That's true moving to any host, not just Rithub — issues and pull requests are GitHub-side metadata, separate from the git repository they're attached to.
Instead of (or alongside) a plain clone, a migration tool authenticates to GitHub's API directly and pulls the repository's issues, pull requests, and related records along with the git history. Gitea — the engine Rithub's current server runs on — ships exactly this as a built-in migration form: point it at a GitHub repo, supply your GitHub username and a personal access token, and it imports history together with the metadata that a plain git clone would leave behind. Gitea's own docs are explicit that pulling in "issues, pull requests, etc." requires at least that username/token, not just a repo URL.
A fast mirror push still gets you working again immediately — see the emergency checklist — with the full issues/PR import done as a follow-up once things have calmed down.
Sign up freeImport from GitHub