From a2e4ecaa52c4593f0455fbcf726e19ec4d7084db Mon Sep 17 00:00:00 2001 From: Felix S Klock II Date: Mon, 17 Jun 2013 10:43:46 -0700 Subject: [PATCH] adding clarifcation since my instinct in the past has been to put the "@bors: retry" messages on the PR rather than the commit --- Note-bors-usage.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Note-bors-usage.md b/Note-bors-usage.md index 7ddf155..950590d 100644 --- a/Note-bors-usage.md +++ b/Note-bors-usage.md @@ -42,7 +42,9 @@ _exactly_ the bits that tested OK. It retries if you move incoming while it's working, so tends to behave "mostly gracefully" with respect to disruption around it. If it misbehaves, it can be provoked to retry a commit with a comment from a -reviewer saying "@bors: retry". It ignores comments by non-reviewers. It +reviewer saying "@bors: retry" (on that same commit as the original "r+", as +opposed to the comment-trail inlined the Pull Request itself). +It ignores comments by non-reviewers. It also does not merge "updates" to a pull request. It considers comments on commits only, not pull requests; if you update a pull request to contain new commits, they need to be reviewed anew.