Part of Empire Cloud

Moving from GitHub to EmpireGit: a checklist

  1. List what you have. Write down every repository, who needs access, and which ones run CI. Start with one low-risk repository.
  2. Make a read-only token on GitHub. The importer needs it to copy issues and pull requests, not just the code.
  3. Run the importer. In Forgejo choose New migration, pick GitHub, and tick what you want copied: issues, pull requests, labels, milestones, releases, wiki.
  4. Check the copy. Compare branch lists and open a couple of old pull requests. Fix anything odd before you move the next repository.
  5. Bring your CI over. Forgejo Actions reads workflow files from .forgejo/workflows and .github/workflows. Most simple jobs run after you register a runner. Test each one.
  6. Register your runners. CI runs on machines you control, so install the runner on them and point it at your server.
  7. Switch remotes. Everyone runs git remote set-url origin <new url>. Do it in one sitting so nobody pushes to the old place.
  8. Archive the old repository. Keep it read-only for a few weeks, then decide whether to delete it.

Ready to try it? See the Team plan