Migration Summary

[6543]

Supported Migration Routines:

• Github (wiki,issue,pr,reviews,reactions) (Improve migrations to support migrating milestones/labels/issues/comments/pullrequests #6290) (Migrate reviews when migrating repository from github #9463) (Migrate reactions when migrating repository from github #9599)
• GitHub Enterprice ( GitHub Migrations for Enterprise GitHub servers #11815)
• Gitlab (Add support for migrating from Gitlab #9084, When migrating from Gitlab map Approvals to approving Reviews #11147) (self-hosted Add a migrate service type switch page #12697)
• Gitea (Please implement migration features Gitea -> Gitea as available for Github -> Gitea #8380, Gitea 2 Gitea migration #12657)
• Codebase (Add migrate from Codebase #16768)
• Phabricator (Add support to migrate from Phabricator #20344)
• Gitee (Migrate issues/wiki/PRs from Gitee #15945)
• Azure DevOps
• Gogs (Add support to migrate from gogs #14342)
• Bitbucket (Migrate from Bitbucket #12919)
• Trac (Migrating from Trac #6908) (https://github.com/stevejefferson/trac2gitea)
• Sourcehut cli tool
• Bugzilla (Import issues from Bugzilla #7802)
• RhodeCode
• OneDev (Add migrate from OneDev #16356)
• GitBucket (Add migration from GitBucket #16767)
• Apache Allura
• launchpad sample go code: in git-bug

Features missing on all platform:

• Projects Support to migrate projects information from github/gitea #12679 WIP: Add github projects migrations support #12819
• Migrate Issues to exist repository [Feature] Migration Issues to existing Repo #10027
• Migrate and Mirror with LFS [Feature] LFS support for Migrate and Mirror #9939 Repo mirroring doesn't mirror LFS data. #849
• Migrate git via SSH Migrate from SSH #1635
• Bulk importing of repositories feature, bulk importing of repositories #2569

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

Partial Imports ..

• Import projects/issues from YouTrack

[6543]

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

[lunny]

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

[stale]

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 #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 :)

[bjornbouetsmith]

Hi,
Any plans to support migration from on prem Azure DevOps (git) to gitea?

I have tried and it just fails - possibly because authentication in azure devops is not using basic authentication but something else?

It just logs:

May 19 18:15:27 git gitea[687]: #033[36m2022/05/19 18:15:27 #033[0m#033[32m...ervices/task/task.go:56:#033[32mhandle()#033[0m #033[1;31m[E]#033[0m Run task failed: #033[1mAuthentication failed: Clone: exit status 128 - fatal: Authentication failed for 'http:https://devops.root.dom/ROOT/common/_git/Helm/'

I am 100% certain that the username/password combo is correct, since I use it on a daily basis - and also can access the repo from another service - using the exact same combo.

I also have this in my app.ini

[migrations]
ALLOW_LOCALNETWORKS = true

My guess is that it is probably because I have a "special" character in my password and when I turn on debug logging I can see the url it tries to clone - and if I copy/paste that URL and do a manual git clone from the prompt - I also get the same:

fatal: Authentication failed for 'http:https://devops.root.dom/ROOT/common/_git/Helm/'

If I do a

git clone http:https://root%[email protected]/ROOT/common/_git/Helm

And manually type in the password - it just works.

I have no idea if its some kind of escaping that happens that messes up the http request inside git - or if its simply wrongly escaped from gitea's side.

Do I just have to accept this?

According to "people" on the internet, then it seems to have been escaped correctly according to https://en.wikipedia.org/wiki/Percent-encoding - but no dice - I have used other systems in the past that did not like my password.

To give a hint about what character that messes it up - its # - which I know is bad in a url - but I refuse to change my password just because some systems do not like it.

wget on the other hand just accepts the encoded url - so I am beginning to think its a bug in git.

Edit:

Just tested on a windows machine and git clone just works with the encoded url (git version 2.33) - on the gitea server (Rocky Linux) - git version 2.27.0 it fails - so either its a bug that is fixed in 2.33 - or an OS issue that is causing this.

Edit2:
Updated git to version 2.31 on the server - and its the same issue. So I am thinking its a git on linux issue.

[6543]

if it's about "raw GIT" migration ... I think it's a bugreport ... nothing we should track here @bjornbouetsmith - could you create a new issue with the info you posted here :) (github should be able to make your comment a own issue)

[bjornbouetsmith]

if it's about "raw GIT" migration ... I think it's a bugreport ... nothing we should track here @bjornbouetsmith - could you create a new issue with the info you posted here :) (github should be able to make your comment a own issue)

Done #19772 - Although I am beginning to think its not a gitea issue - and just a git on linux issue

[woj-tek]

Suggestion: Import projects/issues from youtrack