Rithub's built-in migration form moves a repository's full history — every branch, every tag, every commit — in one form submission, no terminal required. We tested it end to end against a real public GitHub repo: account creation, picking GitHub as the source, pasting a URL, one click to migrate. The migration itself finished well under a minute for a small repo; the whole flow below, done once by a first-timer reading every word, fits inside five minutes.
https://github.com/you/your-repo.git), give it a name, click Migrate Repository. Rithub clones the full history server-side and reports back when it's done — no local git client needed for this path.The same migration, done manually, for a repeatable mirror you can re-run later:
git clone --mirror https://github.com/you/your-repo.git cd your-repo.git git push --mirror https://rithub.dev/you/your-repo.git
Re-run the same git push --mirror line any time you want to re-sync later commits from GitHub.
The migration form brings over git history, and (depending on what you tick) issues, pull requests, and wiki pages where the source supports exporting them. It does not bring over GitHub-specific things that have no git equivalent: GitHub Actions marketplace integrations, branch-protection rule configuration, and org-level settings — those are a one-time manual setup on the new side, not a blocker to moving the code itself.
Create a Rithub accountAlready flagged or suspended on GitHub and need to move urgently? See the emergency checklist.