-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Migration Summary #8689
Comments
And Gitea/Gogs, I have sent a WIP PR to support Gogs. |
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. |
I like to migrate from bitbucket server. BTW: i'm also interested to migrating from a gitlab self-hostet instance. 🙃 |
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. |
@6543 I would like to rename this one as a |
@lunny feel free to change it at any time :) |
Hi, I have tried and it just fails - possibly because authentication in azure devops is not using basic authentication but something else? It just logs:
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
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:
If I do a git clone 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 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: |
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 |
Suggestion: Import projects/issues from youtrack |
Supported Migration Routines:
Features missing on all platform:
this will make the whole system more federated again ... sourcecode is - issues not
Partial Imports ..
The text was updated successfully, but these errors were encountered: