summaryrefslogtreecommitdiff
path: root/doc/development
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-01-07 18:07:34 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2020-01-07 18:07:34 +0000
commit8dafc3b65aeb8f50fdfc38fb98d96c3db9e2f607 (patch)
treeecc8ff28071e68108aea21380d80132e388d48bf /doc/development
parentb4028d450087e97f26d4baa23e08396bcbabe3e0 (diff)
downloadgitlab-ce-8dafc3b65aeb8f50fdfc38fb98d96c3db9e2f607.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development')
-rw-r--r--doc/development/code_review.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/development/code_review.md b/doc/development/code_review.md
index c21b9912e8f..445feba384b 100644
--- a/doc/development/code_review.md
+++ b/doc/development/code_review.md
@@ -274,6 +274,12 @@ time frame, let the author know as soon as possible and try to help them find
another reviewer or maintainer who will be able to, so that they can be unblocked
and get on with their work quickly.
+If you think you are at capacity and are unable to accept any more reviews until
+some have been completed, communicate this through your GitLab status by setting
+the `:red_circle:` emoji and mentioning that you are at capacity in the status
+text. This will guide contributors to pick a different reviewer, helping us to
+meet the SLO.
+
Of course, if you are out of office and have
[communicated](https://about.gitlab.com/handbook/paid-time-off/#communicating-your-time-off)
this through your GitLab.com Status, authors are expected to realize this and