-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Migrating repo from GitLab fails if Wiki is checked #19545
Comments
-> this is is happening because the "wiki" is activated in gitlab but it's an empty git issue if you like to clone it |
https://gitlab.com/interpeer/caprock/-/wikis/home it still looks empty, so probably can be checked via API? I'm just wondering if another error could occur on cloning an existing wiki and would not be detected with your change. |
@fnetX blame gitlab, yes you can check via API - but it wont tell you anything about the state (if initialized or empty) |
my pull #19563 does fix by the way ... |
* giteaofficial/main: Avoid MoreThanOne Error (go-gitea#19557) [skip ci] Updated licenses and gitignores Simplify loops to copy (go-gitea#19569) Use middleware to open gitRepo (go-gitea#19559) Added X-Mailer header to outgoing emails (go-gitea#19562) fix go-gitea#19545 (go-gitea#19563) [skip ci] Updated translations via Crowdin Respect DefaultUserIsRestricted system default when creating new user (go-gitea#19310) Mute link in diff header (go-gitea#19556) Add API to query collaborators permission for a repository (go-gitea#18761) Permalink files In PR diff (go-gitea#19534) Fix Pull Request comment filename word breaks (go-gitea#19535) Don't error when branch's commit doesn't exist (go-gitea#19547)
Description
Migrating repos from GitLab fails if the user ticks the "wiki" option in Gitea, tested from https://gitlab.com/interpeer/caprock which was reported on https://Codeberg.org
It works fine if the "wiki" checkbox is left unticked. Probably a check is missing that the wiki exists // what is the branch.
log excerpt (seems relevant):
Gitea Version
1.17.0+dev-491-g8eb1cd926
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Codeberg deployment + try.gitea.io
Database
No response
The text was updated successfully, but these errors were encountered: