2 title: Reviewing Changes
5 1. Click on a link for incoming or outgoing review.
7 2. The details of the change and its current status are loaded:
9 ![review](images/review.png)
11 - **Status:** Displays the current status of the change.
13 - **Reply:** Click on this button after reviewing to add a final review
14 message and a score, -1, 0 or +1.
16 - **Patch Sets:** If multiple revisions of a patch exist, this button
17 enables navigation among revisions to see the changes. By default,
18 the most recent revision is presented.
20 - **Download:** This button brings up another window with multiple
21 options to download or checkout the current changeset. The button on
22 the right copies the line to your clipboard. You can easily paste it
23 into your git interface to work with the patch as you prefer.
25 Underneath the commit information, the files that have been changed by
26 this patch are displayed.
28 3. Click on a filename to review it. Select the code base to
29 differentiate against. The default is ``Base`` and it will generally
32 4. The review page presents the changes made to the file. At the top of
33 the review, the presentation shows some general navigation options.
34 Navigate through the patch set using the arrows on the top right
35 corner. It is possible to go to the previous or next file in the set
36 or to return to the main change screen. Click on the yellow sticky
37 pad to add comments to the whole file.
39 The focus of the page is on the comparison window. The changes made are
40 presented in green on the right versus the base version on the left.
41 Double click to highlight the text within the actual change to provide
42 feedback on a specific section of the code. Press *c* once the code is
43 highlighted to add comments to that section.
45 5. After adding the comment, it is saved as a *Draft*.
47 6. Once you have reviewed all files and provided feedback, click the
48 *green up arrow* at the top right to return to the main change page.
49 Click the ``Reply`` button, write some final comments, and submit
50 your score for the patch set. Click ``Post`` to submit the review of
51 each reviewed file, as well as your final comment and score. Gerrit
52 sends an email to the change-submitter and all listed reviewers.
53 Finally, it logs the review for future reference. All individual
54 comments are saved as *Draft* until the ``Post`` button is clicked.