bors now accepts
batch commands (which do the same thing) in pull request comments.
If a PR is marked as
rollup, its priority is implicitly set to
-1, which means that the testing of the PR will be postponed until all other “normal” PRs are tested. When one of the rollup PRs hits the top of the queue (which means no other normal PRs are there), bors will merge all of the rollup PRs together and test them as a whole basis. This will reduce unnecessary CPU time to test one-liner doc fixes and minor changes that are not likely to break things (which is why we’ve had manual rollups).
However, you can also manually trigger the rollup even when there are one or more normal PRs. Just set p=[Very high number, such as 765] to one of the rollup PRs. bors will place it at the top of the queue and make a rollup immediately.
Note that the
rollup command is independent to other commands, just like
p=. You can add or remove the rollup tag at any time.
The rollup feature has been only added to the
rust branch of bors. As the
master branch got diverged a bit, we cannot apply these changes to
master directly. It would be great to see both branches got unified someday.