Gitea: Migration Summary

[6543]

Supported Migration Routines:

• [x] Github (wiki,issue,pr,reviews,reactions) (#6290) (#9463) (#9599)
• [x] GitHub Enterprice ( #11815)
• [x] Gitlab (#9084, #11147) (self-hosted #12697)
• [x] Gitea (#8380, #12657)
• [ ] [Azure DevOps](https://azure.microsoft.com/en-us/services/devops/)
• [ ] Gogs (#7181)
• [ ] Bitbucket (#12919)
• [ ] Trac (#6908) (https://github.com/stevejefferson/trac2gitea)
• [ ] [Sourcehut](https://man.sr.ht/todo.sr.ht/api.md) cli tool
• [ ] Bugzilla (#7802)
• [ ] RhodeCode
• [ ] [Apache Allura](https://forge-allura.apache.org/p/allura/wiki/Home)
• [ ] [launchpad](https://launchpad.net/) sample go code: in git-bug

Features missing on all platform:

• [ ] Projects #12679 #12819
• [ ] Migrate Issues to exist repository #10027
• [ ] Migrate and Mirror with LFS #9939 #849
• [ ] Migrate git via SSH #1635
• [ ] Bulk importing of repositories #2569
• [ ] Mirror issues along with the repo #1876
• [ ] Mirror new-created wiki when repositories migrated #2309
• [ ] Mirror an entire github organization into gitea organization #8424
• [ ] Reverse mirroring #7609

this will make the whole system more federated again ... sourcecode is - issues not

[6543]

note: https://docs.gitea.io/en-us/migrations-interfaces/

[lunny]

And Gitea/Gogs, I have sent a WIP PR to support Gogs.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

[viceice]

I like to migrate from bitbucket server.
I know the api very well, but my go expirience is somehoaw little.
I found a go package for wrapping the api go-bitbucket-v1.
Any hints where to start?

BTW: i'm also interested to migrating from a gitlab self-hostet instance. 🙃

[coldcoff]

See also https://github.com/go-gitea/gitea/issues/11815

When using repository migrations (mirroring) there is already support for public GitHub, that will offer to migrate not only the code, but also Issues, Pull Requests and similar by using the public GitHub API to fetch the additional content.

Please make it possible to do the same also when not using the public GitHub, i.e. the URL "github.com".

There are enterprise GitHub instances out there, typically something like "github.company.com" or so, that will work the same, but they are some "isolated" GitHub.

Currently unfortunately only the code migration is possible from such enterprise GitHub instances.

But as Enterprise GitHub is just "GitHub with different URLs" (and the software version running there is probably a bit older than the public GitHub) the task is hopefully only to make some hardcoded GitHub URLs configurable/extendable.

So it might be a lower hanging fruit. This is not really a new platform / new migration, but an extension to the existing GitHub migration.

[lunny]

@6543 I would like to rename this one as a migrations summary issue includes platforms, features, enhancements links and etc.

[6543]

@lunny feel free to change it at any time :)