Skip to content
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

Closed
lunny opened this issue Dec 26, 2016 · 10 comments
Closed

Migrate issues and wikis options when migrating from github #479

lunny opened this issue Dec 26, 2016 · 10 comments
Labels
type/enhancement An improvement of existing functionality type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Milestone

Comments

@lunny
Copy link
Member

lunny commented Dec 26, 2016

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.

@lunny lunny added type/enhancement An improvement of existing functionality type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels Dec 26, 2016
@lunny lunny added this to the 1.1.0 milestone Dec 26, 2016
@FM-96
Copy link

FM-96 commented Dec 26, 2016

I think Bitbucket and GitLab support would also be great, if that's possible.

@lunny
Copy link
Member Author

lunny commented Dec 26, 2016

If there are APIs, I think it's yes.

@bkcsoft
Copy link
Member

bkcsoft commented Dec 26, 2016

Importing issues and merge requests from GitLab will be a PITA since they have separate indexes. Meaning we'll get collisions everywhere...

@lunny lunny modified the milestones: 1.2.0, 1.1.0 Jan 26, 2017
@dakira
Copy link
Contributor

dakira commented Apr 3, 2017

Here's a script that does this: https://lolg.it/herby/gh2gogs

@lunny lunny modified the milestones: 1.x.x, 1.2.0 Apr 19, 2017
@ryanburnette
Copy link

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.

@dakira
Copy link
Contributor

dakira commented Sep 10, 2018

@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.

@techknowlogick
Copy link
Member

Here is a project that works with Gitea API: https://git.jonasfranz.software/JonasFranzDEV/gitea-github-migrator

@cpetry
Copy link

cpetry commented Oct 29, 2018

Any news on issue migration from gitlab? Some ideas?

@lunny lunny modified the milestones: 1.x.x, 1.9.0 Apr 21, 2019
@lunny
Copy link
Member Author

lunny commented Apr 21, 2019

Will be fixed by #6290

@lunny
Copy link
Member Author

lunny commented Jul 8, 2019

Closed by #6290 in v1.9. @techknowlogick

@lunny lunny closed this as completed Jul 8, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/enhancement An improvement of existing functionality type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

7 participants