blob: cf5de1012caa11cee5812a1de9b698a13bd5dbd2 [file] [log] [blame]
Edwin Kempin3fde7e42016-09-19 15:35:10 +02001= Gerrit Code Review - Robot Comments
2
3Gerrit has special support for inline comments that are generated by
4automated third-party systems, so called "robot comments". For example
5robot comments can be used to represent the results of code analyzers.
6
7In contrast to regular inline comments which are free-text comments,
8robot comments are more structured and can contain additional data,
9such as a robot ID, a robot run ID and a URL, see
10link:rest-api-changes.html#robot-comment-info[RobotCommentInfo] for
11details.
12
13It is planned to visualize robot comments differently in the web UI so
14that they can be easily distinguished from human comments. Users should
15also be able to use filtering on robot comments, so that only part of
16the robot comments or no robot comments are shown. In addition it is
17planned that robot comments can contain fixes, that users can apply by
18a single click.
19
20== REST endpoints
21
22* Posting robot comments is done by the
23 link:rest-api-changes.html[Set Review] REST endpoint. The
24 link:rest-api-changes.html#review-input[input] for this REST endpoint
25 can contain robot comments in its `robot_comments` field.
26* link:rest-api-changes.html#list-robot-comments[List Robot Comments]
27* link:rest-api-changes.html#get-robot-comment[Get Robot Comment]
28
29== Storage
30
31Robot comments are stored per change in a
32`refs/changes/XX/YYYY/robot-comments` ref, where `XX/YYYY` is the
33sharded change ID.
34
35Robot comments can be dropped by deleting this ref.
36
37== Limitations
38
39* Robot comments are only supported with NoteDb, but not with ReviewDb.
40* Robot comments are not displayed in the web UI yet.
41* There is no support for draft robot comments, but robot comments are
42 always published and visible to everyone who can see the change.
43
44GERRIT
45------
46Part of link:index.html[Gerrit Code Review]
47
48SEARCHBOX
49---------