summaryrefslogtreecommitdiffstats
path: root/devtools/docs/contributor/contributing/code-reviews-find-reviewer.md
diff options
context:
space:
mode:
Diffstat (limited to 'devtools/docs/contributor/contributing/code-reviews-find-reviewer.md')
-rw-r--r--devtools/docs/contributor/contributing/code-reviews-find-reviewer.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/devtools/docs/contributor/contributing/code-reviews-find-reviewer.md b/devtools/docs/contributor/contributing/code-reviews-find-reviewer.md
new file mode 100644
index 0000000000..67548b5c30
--- /dev/null
+++ b/devtools/docs/contributor/contributing/code-reviews-find-reviewer.md
@@ -0,0 +1,5 @@
+# Finding suitable reviewers
+
+There are several options to find a good reviewer for a patch. If the bug you are working on is mentored, assign the review to the mentor. Otherwise, assign it to the triage owner (visible in the "People" section of a Bug in Bugzilla).
+
+Finally, an easy option is to use the #devtools-reviewers group in Phabricator.