From 6d5c15d2ca4ce0653ebcfc0c5a9f3ea962d7b9a8 Mon Sep 17 00:00:00 2001 From: Ash McKenzie Date: Fri, 13 Sep 2019 16:15:43 +1000 Subject: Add 'responsibility of the reviewer' section --- doc/development/code_review.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/doc/development/code_review.md b/doc/development/code_review.md index d55623521e1..ce9f794c1a3 100644 --- a/doc/development/code_review.md +++ b/doc/development/code_review.md @@ -127,6 +127,17 @@ through Slack). If you can't assign a merge request, `@` mentioning a maintainer This [saves reviewers time and helps authors catch mistakes earlier](https://www.ibm.com/developerworks/rational/library/11-proven-practices-for-peer-review/index.html#__RefHeading__97_174136755). +### The responsibility of the reviewer + +[Review the merge request](#reviewing-code) thoroughly. When you are confident +that it meets all requirements, you should: + +- Click the Approve button. +- Advise the author their merge request has been reviewed and approved. +- Assign the merge request to a maintainer. [Reviewer roulette](#reviewer-roulette) +should have made a suggestion, but feel free to override if someone else is a +better choice. + ### The responsibility of the maintainer Maintainers are responsible for the overall health, quality, and consistency of -- cgit v1.2.1