IssueTracker

*************************************************************************
*** !!!! 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.
*************************************************************************

What steps will reproduce the problem?
1. Start docker image docker.io/gerritcodereview/gerrit:3.7.0
2. Open Gerrit UI, add your public ssh-key
3. Browse repositories, All-Users, Command, Edit repo config
4. Add a space in the config, save and publish
5. Start the review
6. Connect to Gerrits ssh port to listen on stream-events
7. Click REPLY and add the text 'recheck' in the comment box.
8. Click SEND
9. Look at the commend-added stream event that has been received in the ssh client

What is the expected output?
The commend-added stream-event should contain the key "message"
with the value "Patch Set 1:\n\ntesting"

What do you see instead?
The "message" key has the value "Patch Set 1:\n\n(1 comment)"

Please provide any additional information below.
CI systems like Zuul-CI is commonly configured to listen on comment-added
with a regular expression similar to "(?i)^(Patch Set [0-9]+:)?( [\w\+-]*)*(\n\n)?\s*recheck"
It is used to re trigger checks on a change/patch set.

Zuul-CI has this as an example in their documentation [1]

This works with 3.6.3 and can be verified by running the steps above with that version.

One visible difference is that the UI in 3.7.0 does call the draft endpoint
when you type in the edit box while replying to a change. The json sent to
the review endpoint does not include the comments in this case.
3. 6.3 does not call the draft endpoint and the comment is sent to the review endpoint

[1] https://zuul-ci.org/docs/zuul/latest/drivers/gerrit.html#reference-pipelines-configuration