diff options
author | zeripath <art27@cantab.net> | 2020-11-04 22:55:15 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-11-04 17:55:15 -0500 |
commit | 3cab3bee5750a12da9ef8a9ba5cbe3da00594921 (patch) | |
tree | dadb2ad8b8b52475f3e5464df338161bde612d51 /models/migrations/migrations.go | |
parent | fb756e773831d215fdb807b736d6276012669b6c (diff) | |
download | gitea-3cab3bee5750a12da9ef8a9ba5cbe3da00594921.tar.gz gitea-3cab3bee5750a12da9ef8a9ba5cbe3da00594921.zip |
Replies to outdated code comments should also be outdated (#13217)
* When replying to an outdated comment it should not appear on the files 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>
* fix test
Signed-off-by: Andrew Thornton <art27@cantab.net>
Co-authored-by: techknowlogick <techknowlogick@gitea.io>
Diffstat (limited to 'models/migrations/migrations.go')
-rw-r--r-- | models/migrations/migrations.go | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/models/migrations/migrations.go b/models/migrations/migrations.go index cbf8ae8732..4715f192c1 100644 --- a/models/migrations/migrations.go +++ b/models/migrations/migrations.go @@ -250,6 +250,8 @@ var migrations = []Migration{ NewMigration("fix publisher ID for tag releases", fixPublisherIDforTagReleases), // v157 -> v158 NewMigration("ensure repo topics are up-to-date", fixRepoTopics), + // v158 -> v159 + NewMigration("code comment replies should have the commitID of the review they are replying to", updateCodeCommentReplies), } // GetCurrentDBVersion returns the current db version |