To batch migrate GitHub to Gitea, migtea gets you past one small limit: Gitea’s built-in migrator moves exactly one repository per submission. migtea is an open-source terminal tool I built that moves your whole account in one pass, wikis, LFS, and issues included. Here is how it works, screen by screen.
Everything here was tested against Gitea 1.26.4, gh 2.96.0, tea 0.12.0, and uv 0.11.2.
Key Takeaways
- Gitea’s migrator moves one repo per submission and has no batch mode.
- One migration carries code, wiki, LFS, issues, and pull requests.
uvx migteabatch-migrates every repo with nothing to install.- Preflight, diff, tick, confirm: four screens from zero to migrated.
gh auth tokenlets Gitea clone private repos and dodge rate limits.
Why won’t Gitea migrate all your GitHub repos at once?
Gitea has a built-in migration page, but it moves only one repository at a time. You paste one GitHub URL and a token, click Migrate, and wait. The repo arrives complete, with its wiki, LFS objects, and issues. Then you start over with the next one. For a hundred repos, that is a hundred rounds of the same form. migtea does them all in one go.
Botmonster Tech




