Migration from github results in http code 500
I am thinking about migrating my github repositories to codeberg. I tried a new migration with the webfrontend („Neue Migration“), but this results in a server error 500 for one repository when including the issues. Migrating without „issues“ seems to work - but I really would like to keep the issues and the according comments/conversations.
The repository which doesn‘t want to migrate is: https://github.com/BernieO/calcardbackup
I also tried a migration via command line, but that results in a 403. Unfortunately the documentation of the gitea-Migrator is not a big help: https://gitea.com/gitea/migrator/src/branch/master/README.md
What can I do?
I found out what the problem is, thank you for reporting the issue. The problem is an emoji inside the issue comments 😞
It is linked to this change:
We have to migrate codeberg carefully and to tests, but I think this is really high priority! Thanks for reporting again!
I have sucessfully fixed the problem on codeberg-test.org (which is ok to fully crash and burn) but I will need to find a calm moments and four eyes for doing this operation on codeberg.org
Fixed. The proof is here: 👍 (this led to 500 before).
Can you try again? Also please not that the migration on codeberg-test is far more advanced (the issue comments will be marked as "from github" and can potentially be transferred to codeberg users later, while the migration on codeberg only writes "Author: @xyz" inside the issue comment and assigns the comment to you (the migrator)
Thanks for the quick patch - migrating https://github.com/BernieO/calcardbackup now works without any issues (including emoticons in comments) 😄
Also please not that the migration on codeberg-test is far more advanced (the issue comments will be marked as “from github” and can potentially be transferred to codeberg users later, while the migration on codeberg only writes “Author: @xyz” inside the issue comment and assigns the comment to you (the migrator)
I am interested in this feature as well (comments will be marked as „from github“).
What is the timeline for integrating this more advanced migration tool to codeberg.org?
The migration improvements are part of gitea 1.10 which is work in progress and my personal guess is that it might be out in October.
While I want to have this feature ASAP I do not think it is wise to deploy a WIP gitea release on Codeberg. Usually we test early release candidates extensively on codeberg-test.org and deploy them if everything looks good before the official final version.
Deleting a branch is permanent. It CANNOT be undone. Continue?