Earl Warren 603a44edf0 [GITEA] POST /repos/{owner}/{repo}/pulls/{index}/reviews/{id}/comments ... Refs: https://codeberg.org/forgejo/forgejo/issues/2109 (cherry picked from commit 8b4ba3dce7) (cherry picked from commit 196edea0f9) [GITEA] POST /repos/{owner}/{repo}/pulls/{index}/reviews/{id}/comments (squash) do not implicitly create a review If a comment already exists in a review, the comment is added. If it is the first comment added to a review, it will implicitly create a new review instead of adding to the existing one. The pull_service.CreateCodeComment function is responsibe for this behavior and it will defer to createCodeComment once the review is determined, either because it was found or because it was created. Rename createCodeComment into CreateCodeCommentKnownReviewID to expose it and change the API endpoint to use it instead. Since the review is provided by the user and verified to exist already, there is no need for the logic implemented by CreateCodeComment. The tests are modified to remove the initial comment from the fixture because it was creating the false positive. I was verified to fail without this fix. (cherry picked from commit 6a555996dc) (cherry picked from commit b173a0ccee) (cherry picked from commit 838ab9740a)		2024-02-05 16:09:42 +01:00
..
actions	Add artifacts v4 jwt to job message and accept it (#28885)	2024-02-02 14:25:59 +00:00
forgejo/v1	[CLEANUP] Reuse ForgejoVersion variable	2024-02-05 14:45:11 +01:00
packages	[GITEA] Drop sha256-simd in favor of stdlib	2024-02-05 16:09:40 +01:00
v1	[GITEA] POST /repos/{owner}/{repo}/pulls/{index}/reviews/{id}/comments	2024-02-05 16:09:42 +01:00