Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
The version field defines the version of the software the bug was found in. [ID: 1154637]
View issue level access limits(Press Alt + Right arrow for more information)
Attachment actions
Unintended behavior
View staffing
Description
*************************************************************************
*** !!!! THIS BUG TRACKER IS FOR GERRIT CODE REVIEW !!!!
*** Do not submit bugs for chrome/android and issues with your company's
*** Gerrit setup here. Those issues belong in different issue trackers.
*************************************************************************
Affected Version: 3.0.11
What steps will reproduce the problem?https://gerrit/a/changes/1234/revisions/1/drafts -d @draft.json -H "content-type: application/json; charset=UTF-8" -H "accept: application/json"https://gerrit/a/changes/1234/revisions/1/review -d @reviewPublishDrafts.json -H "Content-Type: application/json"https://gerrit/a/changes/1234/revisions/1/review -d @reviewWithComments.json -H "Content-Type: application/json"
1. Create a change merging a branch into another one (i.e. a merge commit)
2. Notice that by default, the change just has the commit message and the merge list listed as files. Only when changing the displayed base from "Auto Merge" to "Parent 1" you get a list of all files contained in the change.
3. Create a draft comment on a file in the change that is only displayed when selecting another base than "Auto Merge", either via the UI or the REST API - e.g. using curl:
curl -X PUT
4. Submit the review containing the draft comment, either via the UI or the REST API - e.g. using curl:
curl -X POST
5. Refresh the UI and notice that the comment was posted and is visible on the file.
4. Send another review directly containing a file comment instead of drafting it first to the change via the REST API - e.g. using curl:
curl -X POST
What is the expected output?
Another review has been added to the change and the comment is posted and visible on the file.
What do you see instead?
The REST API request fails with HTTP error 400 and the message "file project/src/main/java/some/package/NewFile.java not found in revision 1234,1."
Please provide any additional information below.
This behavior also occurs for robot comments, with the additional predicament that for those, drafting is not supported and there is no way to add robot comments to files in merge commits.