Migrate From GitHub to Self-Hosted Git

Migrating from GitHub to a self-hosted git host is a mirror push, not a rewrite. Your full commit history, branches, and tags move over exactly as they are. Rithub is a self-hosted destination that speaks the same git protocol GitHub does.

Why teams migrate off GitHub

Step-by-step migration

  1. Clone (or use your existing clone of) the GitHub repository:
    git clone https://github.com/<you>/<repo>.git
  2. Create the destination repository on Rithub, then add it as a second remote:
    git remote add rithub https://git.ereboslab.com/<you>/<repo>.git
  3. Mirror every branch and tag in one push -- this is the whole migration:
    git push rithub --mirror
  4. Verify the history matches on both remotes:
    git log --oneline -5   # same output on github and rithub remotes
  5. Point CI, webhooks, and your team's default origin at Rithub once verified. Keep GitHub as a read-only mirror for as long as you like, or remove it.

Frequently asked questions

How do I migrate a repository from GitHub to self-hosted git?
Add the self-hosted host as a second remote, run git push --mirror, then verify history matches before switching origin.

Does migrating lose issues or pull requests?
Code, commits, branches, and tags never get lost -- a mirror push carries all of it. Issues/PRs are GitHub metadata and need a separate export if you want them carried over too.

Can I migrate without downtime?
Yes -- keep using GitHub while you mirror, verify, then switch over whenever ready.

What do I get after migrating to Rithub?
The same clone/push/pull/PR/issue workflow, plus a package registry and self-hosted CI, under our own domain.

See repositories already running on Rithub

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