Skip to content

Commit beb121f

Browse files
[Docs] Instructions for new contributors to find reviewers (llvm#71936)
Right now, the documentation does not clarify what new contributors should do to find potential reviewers, since new contributors don't have write access and thus cannot select them as explained in the docs. This patch extends the guidelines for new people, as discussed in https://discourse.llvm.org/t/how-to-find-reviewers/74803
1 parent 4e67234 commit beb121f

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

llvm/docs/Contributing.rst

+4-1
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,10 @@ To make sure the right people see your patch, please select suitable reviewers
9898
and add them to your patch when requesting a review. Suitable reviewers are the
9999
code owner (see CODE_OWNERS.txt) and other people doing work in the area your
100100
patch touches. Github will normally suggest some reviewers based on rules or
101-
people that have worked on the code before.
101+
people that have worked on the code before. If you are a new contributor, you
102+
will not be able to select reviewers in such a way, in which case you can still
103+
get the attention of potential reviewers by CC'ing them in a comment -- just
104+
@name them.
102105

103106
A reviewer may request changes or ask questions during the review. If you are
104107
uncertain on how to provide test cases, documentation, etc., feel free to ask

0 commit comments

Comments
 (0)