-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Comments on review should have the same sha #13448
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
Comments on review should have the same sha #13448
Conversation
…s page This happened because the comment took the latest commitID as its base instead of the reviewID that it was replying to. There was also no way of creating an already outdated comment - and a reply to a review on an outdated line should be outdated. Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
Whilst the migration was broken the correct solution should have been to no-op the migration not revert the whole commit. In any case hopefully this fixes the migration. |
…com:zeripath/gitea into comments-on-review-should-have-the-same-sha
CI randomly failed but may not relate to this. |
Unfortunately the mssql code is incorrect |
mssql: Only one expression can be specified in the select list when the subquery is not introduced with EXISTS. |
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
🚀 |
This may have caused a regression in 1.13 #13683. Could someone have a look at that? |
Restore #13217