Skip to content

Commit 5c90811

Browse files
authored
Rollup merge of #66826 - mlodato517:mlodato517-clarify-pr-message-assigner, r=Dylan-DPC
Clarifies how to tag users for assigning PRs Clarifies language of where to put `r?` text to assign a particular user. Mostly a follow up of [this discussion](#66797 (comment)).
2 parents 0f6e636 + 77f2ac4 commit 5c90811

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

CONTRIBUTING.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -150,13 +150,13 @@ All pull requests are reviewed by another person. We have a bot,
150150
request.
151151

152152
If you want to request that a specific person reviews your pull request,
153-
you can add an `r?` to the message. For example, [Steve][steveklabnik] usually reviews
153+
you can add an `r?` to the pull request description. For example, [Steve][steveklabnik] usually reviews
154154
documentation changes. So if you were to make a documentation change, add
155155

156156
r? @steveklabnik
157157

158-
to the end of the message, and @rust-highfive will assign [@steveklabnik][steveklabnik] instead
159-
of a random person. This is entirely optional.
158+
to the end of the pull request description, and [@rust-highfive][rust-highfive] will assign
159+
[@steveklabnik][steveklabnik] instead of a random person. This is entirely optional.
160160

161161
After someone has reviewed your pull request, they will leave an annotation
162162
on the pull request with an `r+`. It will look something like this:

0 commit comments

Comments
 (0)