Gitea: [Feature] Migration Issues to existing Repo

[6543]

allow migration of Issues, Milestone and Lables to an existing repo

[guillep2k]

What it the use case?

[6543]

if you have your code managed on one repo and issues are managed elswhere ... later you decide to move all into one place

[lunny]

I think you could force push the git repository to the new migrated repository.

[6543]

in the case this feature come up with (#10031) i cant ...

[schoel-bis]

To give you another use case: We have several projects that are spread out over multiple repositories, typically one for the server component and one for the UI component, but sometimes also more than that. Now, we encourage users to use our Gitea to report issues. Of course, they will almost always report issues against the UI component since that is what they interact with. Yet, from a developer perspective, many of these issues actually belong to the server component as that is where the action takes place. Currently, we have to copy/paste the issue to the server component or cross-reference issues, commits, and pull-requests between the repos. It would be much more convenient if we could just simple move/transfer the issue to the other repo. Ideally, the URL for the original issue would forward to the new location so that end users reporting an issue would still be able to find it after transfer.

GitHub does have a “Transfer issue” feature.

[aschrijver]

My use case is as follows: I've been developing a website on my local self-hosted gitea instance, and soon I want to migrate it to codeberg.org. But all the commits I have made thus far contain reference to issue ID's in the message line. A simple push of the repo to the new origin at codeberg would create a mess with wrong commits showing up on the various issues, both open and closed. The only option I see now is to manually fully recreate the issues I have locally atm.

[6543]

@aschrijver can tea do the job for you?

[aschrijver]

Thanks for the suggestion. Taking a quick peek at the code, I think it is insufficient.

[guillep2k]

@aschrijver This issue is about migrating issues between repos within Gitea.

[6543]

It still is ...

[aschrijver]

@guillep2k you mean within the same host server? I want to migrate from a local self-hosted gitea to a remote gitea (hosted at codeberg.org).

[guillep2k]

@aschrijver Sorry, I didn't realize codeberg.org was running Gitea. 😅

[6543]

@aschrijver a nother workaround could be to use Giteas API to export import it ... since I noticed tea only "export" issue but do not import it - but this is only a workaround ...

while this issue here stands for a feature to migrate issues to an existing repo from somewhere else

... I'm actualy thinking this is not needed anymore more importand would be to fix #10031, and a migration function within gitea from one repo to another one ...

@guillep2k should I close?

[6543]

you can use the migration function and force push code afterwards if needed ... only one idear: an option to NOT migrate code but other stuff if github or gitlab is selected ...

[aschrijver]

Thanks for your suggestions, @6543