-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate issues and wikis options when migrating from github #479
Comments
I think Bitbucket and GitLab support would also be great, if that's possible. |
If there are APIs, I think it's yes. |
Importing issues and merge requests from GitLab will be a PITA since they have separate indexes. Meaning we'll get collisions everywhere... |
Here's a script that does this: https://lolg.it/herby/gh2gogs |
I'm pretty desperate for a way to migrate issues from Github to Gitea. I'd donate or pay a bounty for the feature. I checked into herby/gh2gogs, but it wasn't clear to me how to use that library. |
@ryanburnette You can get an export tarball somewhere from github. If I remember correctly you also get that through the Github API. The script (which needs to be run with nodejs) just goes through the tarball and uses the Gogs API to create all the issues and pullrequests. I'd much rather write something that adds this directly to the DB. Should be quite easy, really. |
Here is a project that works with Gitea API: https://git.jonasfranz.software/JonasFranzDEV/gitea-github-migrator |
Any news on issue migration from gitlab? Some ideas? |
Will be fixed by #6290 |
Closed by #6290 in v1.9. @techknowlogick |
On migrate UI, we could provide checkboxes to issues and wikis when the clone URL is a github URL and after that be checked. wikis and issues will both be migrated when codes migrated.
The text was updated successfully, but these errors were encountered: