github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-21 03:14:01 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Migration Summary #4187

New Issue
Open
opened 2025-11-02 05:41:44 -06:00 by GiteaMirror · 11 comments
GiteaMirror commented 2025-11-02 05:41:44 -06:00
Owner
Copy Link

Originally created by @6543 on GitHub (Oct 25, 2019).

Supported Migration Routines:

Features missing on all platform:

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

Partial Imports ..

Originally created by @6543 on GitHub (Oct 25, 2019). ## 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) * [x] Codebase (#16768) * [ ] [Phabricator](https://github.com/phacility/phabricator) (#20344) * [ ] Gitee (#15945) * [ ] [Azure DevOps](https://azure.microsoft.com/en-us/services/devops/) * [x] Gogs (#14342) * [ ] Bitbucket (#12919) * [ ] Trac (#6908) (https://github.com/stevejefferson/trac2gitea) * [ ] [Sourcehut](https://man.sr.ht/todo.sr.ht/api.md) [cli tool](https://github.com/xenrox/srhtctl) * [ ] Bugzilla (#7802) * [ ] RhodeCode * [x] OneDev (#16356) * [x] GitBucket (#16767) * [ ] [Apache Allura](https://forge-allura.apache.org/p/allura/wiki/Home) * [ ] [launchpad](https://launchpad.net/) sample go code: [in git-bug](https://github.com/MichaelMure/git-bug/tree/master/bridge/launchpad) ## Features missing on all platform: * [ ] Projects #12679 #12819 * [ ] Migrate Issues to exist repository #10027 * [x] Migrate and Mirror with LFS #9939 #849 * [ ] Migrate git via SSH #1635 * [ ] 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](https://www.jetbrains.com/youtrack)
GiteaMirror added the issue/confirmedtopic/repo-migrationtype/summary labels 2025-11-02 05:41:44 -06:00
GiteaMirror commented 2025-11-02 05:41:45 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Oct 25, 2019):

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

@6543 commented on GitHub (Oct 25, 2019): note: https://docs.gitea.io/en-us/migrations-interfaces/
GiteaMirror commented 2025-11-02 05:41:45 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Oct 26, 2019):

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

@lunny commented on GitHub (Oct 26, 2019): And Gitea/Gogs, I have sent a WIP PR to support Gogs.
GiteaMirror commented 2025-11-02 05:41:45 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 28, 2020):

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.

@stale[bot] commented on GitHub (Mar 28, 2020): 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.
GiteaMirror commented 2025-11-02 05:41:45 -06:00
Author
Owner
Copy Link

@viceice commented on GitHub (Jun 5, 2020):

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

@viceice commented on GitHub (Jun 5, 2020): 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](https://github.com/gfleury/go-bitbucket-v1). Any hints where to start? BTW: i'm also interested to migrating from a gitlab self-hostet instance. 🙃
GiteaMirror commented 2025-11-02 05:41:45 -06:00
Author
Owner
Copy Link

@coldcoff commented on GitHub (Jun 10, 2020):

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.

@coldcoff commented on GitHub (Jun 10, 2020): 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.
GiteaMirror commented 2025-11-02 05:41:46 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Sep 3, 2020):

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

@lunny commented on GitHub (Sep 3, 2020): @6543 I would like to rename this one as a `migrations` summary issue includes platforms, features, enhancements links and etc.
GiteaMirror commented 2025-11-02 05:41:46 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Sep 3, 2020):

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

@6543 commented on GitHub (Sep 3, 2020): @lunny feel free to change it at any time :)
GiteaMirror commented 2025-11-02 05:41:46 -06:00
Author
Owner
Copy Link

@bjornbouetsmith commented on GitHub (May 19, 2022):

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://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://devops.root.dom/ROOT/common/_git/Helm/'

If I do a

git clone http://root%5Cbbs@devops.root.dom/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.

@bjornbouetsmith commented on GitHub (May 19, 2022): 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://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://devops.root.dom/ROOT/common/_git/Helm/' ~~~ If I do a ~~~shell git clone http://root%5Cbbs@devops.root.dom/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.
GiteaMirror commented 2025-11-02 05:41:46 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (May 20, 2022):

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)

@6543 commented on GitHub (May 20, 2022): 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)
GiteaMirror commented 2025-11-02 05:41:47 -06:00
Author
Owner
Copy Link

@bjornbouetsmith commented on GitHub (May 21, 2022):

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

@bjornbouetsmith commented on GitHub (May 21, 2022): > 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
GiteaMirror commented 2025-11-02 05:41:47 -06:00
Author
Owner
Copy Link

@woj-tek commented on GitHub (Jul 5, 2022):

Suggestion: Import projects/issues from youtrack

@woj-tek commented on GitHub (Jul 5, 2022): Suggestion: Import projects/issues from youtrack
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/confirmed topic/repo-migration type/summary
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#4187
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?