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.
git remote add rithub https://git.ereboslab.com/<you>/<repo>.git
git push rithub --mirrorThis moves every branch and tag, not just the branch you have checked out.
git log --oneline -5 # same top commits on github and rithub git branch -a # same branch list git tag # same tag list
.github/workflows to .gitea/workflows in the repo; most workflow YAML and runs-on: labels carry over unchanged.act_runner register + act_runner daemon), then push a small test workflow and confirm it goes queued → running → success.origin once Rithub is confirmed correct:
git remote set-url origin https://git.ereboslab.com/<you>/<repo>.git
Moves with git push --mirror: full commit history, all branches, all tags Needs separate export: issues, pull requests, GitHub Actions run history, wiki pages
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.
Want an account? Email [email protected] to request access.