diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-10-06 18:09:39 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-10-06 18:09:39 +0300 |
| commit | d4806ad7dbd2d87ae09872709fef1aef35792e21 (patch) | |
| tree | 91c7b62c3a493f3b922ed49e6d8d86d43e04a74c /doc/development/code_review.md | |
| parent | 3e9c050126b34ac4f44ab9f5e4b9ffb48b902c01 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/code_review.md')
| -rw-r--r-- | doc/development/code_review.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/development/code_review.md b/doc/development/code_review.md index bdd2c424687..db0ac4def75 100644 --- a/doc/development/code_review.md +++ b/doc/development/code_review.md @@ -442,8 +442,7 @@ first time. ### Requesting a review When you are ready to have your merge request reviewed, -you should [request an initial review](../user/project/merge_requests/getting_started.md#reviewer) by selecting a reviewer from your group or team. -However, you can also assign it to any reviewer. The list of reviewers can be found on [Engineering projects](https://about.gitlab.com/handbook/engineering/projects/) page. +you should [request an initial review](../user/project/merge_requests/getting_started.md#reviewer) by selecting a reviewer based on the [approval guidelines](#approval-guidelines). When a merge request has multiple areas for review, it is recommended you specify which area a reviewer should be reviewing, and at which stage (first or second). This will help team members who qualify as a reviewer for multiple areas to know which area they're being requested to review. |