github.com/adnan-c/fabric_e2e_couchdb@v0.6.1-preview.0.20170228180935-21ce6b23cf91/docs/Gerrit/reviewing.md (about)

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