GitHub to Rithub Migration Checklist

Work through this checklist top to bottom. Each step includes the real command to run on the live Rithub instance (git.ereboslab.com) and how to verify it worked before moving to the next one.

The checklist

What moves automatically vs. what needs a separate export

Moves with git push --mirror:   full commit history, all branches, all tags
Needs separate export:          issues, pull requests, GitHub Actions run history, wiki pages

Frequently asked questions

Can I sign up for Rithub myself?
Not yet self-serve — registration is by request. Email for an account before starting the checklist.

Will I lose any commits?
No — git push --mirror moves every branch, tag, and commit exactly as it is.

Do issues and pull requests come over automatically?
No — those are GitHub metadata, not git history, and need a separate export.

How do I know the CI migration actually works?
Push a small test workflow after registering a runner and confirm it reports success via the Actions run status, not just that the runner shows online.

See repositories already running on Rithub

Want an account? Email [email protected] to request access.