From 66eb35601df6f472b5e2edf2edc24335dbca0593 Mon Sep 17 00:00:00 2001 From: guineveresaenger Date: Wed, 21 Feb 2018 10:49:26 -0800 Subject: Explains how to assign a reviewer using a bot command Pinging someone with a github mention is different from using a bot command to assign them as a reviewer. This commit includes a specific explanation. --- contributors/guide/pull-requests.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/contributors/guide/pull-requests.md b/contributors/guide/pull-requests.md index 66d55807..c87f74fe 100644 --- a/contributors/guide/pull-requests.md +++ b/contributors/guide/pull-requests.md @@ -142,8 +142,7 @@ There is a detailed rundown of best practices, including how to avoid too-length But, if you've already followed the best practices and you still aren't getting any pull request love, here are some things you can do to move the process along: - * Make sure that your pull request has an assigned reviewer (assignee in GitHub). If not, reply to the pull request comment stream asking for a reviewer to be assigned. - + * Make sure that your pull request has an assigned reviewer (assignee in GitHub). If not, reply to the pull request comment stream asking for a reviewer to be assigned. This is done via a [bot command](https://prow.k8s.io/command-help) (the bot may have suggestions for this) and looks like this: `/assign @username`. * Ping the assignee (@username) on the pull request comment stream, and ask for an estimate of when they can get to the review. -- cgit v1.2.3