Hello,
Github has the ability to export all your data
I’m wondering if there’s anything anyone has already made that is able to migrate everything from that archive into gitea?
as far as i know nothing eats that archive directly. the github user migration export is basically a json dump meant for archiving, gitea has no importer for it.
what gitea does have is the live migration. New Migration, pick GitHub, give it the repo url and a personal access token, and it pulls the repo plus issues, pull requests, labels, milestones, releases and the wiki. that is the path everyone actually uses and it works well. token needs repo scope, and if the source is private you obviously need one that can read it.
if your github account is already gone and the tarball is all you have left, then it is a scripting job. the repos in the archive are bare git dirs so you can just push those up, and then feed the issues json into the gitea api with a small script. there are a few community migrate scripts floating around on github that do issues over the api, quality varies, i would read one before trusting it.
one gotcha even on the good path: rate limits. if you migrate a bunch of repos in a row github will throttle you mid run and gitea marks the migration failed. do them a few at a time.
yeah, I still have the repos on github so I can do the live migration. I imagine I will. The thinking is more that I already have the archive, so it would save on the effort to do the migration for 137 repositories, and the associated rate limit shenanigans.
I couldn’t find anything that already takes into account github archive, but was hoping someone knows of something I couldn’t find.
yeah for 137 repos the tarball wont save you. nothing eats that github export.
keep the archive as a local git backup. then loop the live migrate api with a repo-scope PAT and sleep 45-60s between repos so github doesnt throttle you mid run. if one dies, git push --mirror that repo from the archive by hand.
dont click New Migration 137 times.
1 Like