diff options
| author | varkor <github@varkor.com> | 2019-03-14 01:09:32 +0000 |
|---|---|---|
| committer | varkor <github@varkor.com> | 2019-03-14 01:09:32 +0000 |
| commit | eadb8443f3ea4269b7010afa3bd5de21515c23b1 (patch) | |
| tree | cd0314ce170056610cf61454d4270aedddfe507f /CONTRIBUTING.md | |
| parent | 6f3fda9d1d603084c8e6a323bdbea7b780ba87ca (diff) | |
| download | rust-eadb8443f3ea4269b7010afa3bd5de21515c23b1.tar.gz | |
Update r+ syntax
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index dde4ac3bbeb..5276171728f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -147,7 +147,7 @@ of a random person. This is entirely optional. After someone has reviewed your pull request, they will leave an annotation on the pull request with an `r+`. It will look something like this: - @bors: r+ 38fe8d2 + @bors r+ This tells [@bors][bors], our lovable integration bot, that your pull request has been approved. The PR then enters the [merge queue][merge-queue], where @bors @@ -302,7 +302,7 @@ from the source code itself. Documentation pull requests function in the same way as other pull requests, though you may see a slightly different form of `r+`: - @bors: r+ 38fe8d2 rollup + @bors r+ rollup That additional `rollup` tells @bors that this change is eligible for a 'rollup'. To save @bors some work, and to get small changes through more quickly, when |