Migrate GitHub Releases to Another Host

A release's tag moves with a git clone, but the release itself — title, notes, attached binaries — is a separate GitHub object that a plain clone leaves behind. Rithub's GitHub import pulls releases over as part of the same migration as code, issues, and the rest.

Why releases need more than a clone

Git tags are part of the repository and travel with any clone or mirror push. A GitHub release is a layer on top of a tag — the release notes and any uploaded binary assets are stored by GitHub separately and only reachable through its API. Moving releases means calling that API, not just copying git objects.

What Rithub's import brings over

FieldPreserved
Release tagYes (comes with the git history)
Release title and notesYes
Draft / pre-release flagsYes
Attached binary assetsYes

This is part of the same one-click import covered in the full migration checklist — releases, issues, pull requests, labels, milestones, and the wiki all move together with code and history.

Staying current after the first import

If you import as a mirror rather than a one-time copy, Rithub automatically re-syncs from GitHub every 8 hours (see keeping a repo auto-mirrored), so releases you publish on GitHub later keep showing up on the Rithub side without running the import again.

Import a repo + releases from GitHub Sign up free