-
-
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
Migration failure during reaction migration from gitea (#13344) #13346
Migration failure during reaction migration from gitea (#13344) #13346
Conversation
* Migrating reactions is just not that important A failure during migrating reactions should not cause failure of migration. Signed-off-by: Andrew Thornton <art27@cantab.net> * When checking issue reactions check the correct permission Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: techknowlogick <techknowlogick@gitea.io>
Closing this as Gitea migration isn't in 1.12 |
No but the reactions API is and it is those fixes which needs to be backported |
Ah yes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is missing the issue comment reactions changes
@zeripath those aren't included because |
Adding blocked label |
Nope it's not that - unfortunately both the original and the 1.13 backport were missing one final change that I thought I had pushed up. Line 60 of the issue_reaction.go has the same bug and also needs to be fixed. |
Unfortunately my final push to go-gitea#13344 didn't register - or I failed to push it properly. GetIssueCommentReactions in routers/api/v1/repo/issue_reaction.go also makes the same mistake.
A failure during migrating reactions should not cause failure of
migration.
Signed-off-by: Andrew Thornton art27@cantab.net
Signed-off-by: Andrew Thornton art27@cantab.net
Credit @zeripath