bors
bors copied to clipboard
graydon
Integration robot for buildbot and github
Rust frequently has a dozen small PR's in the queue and we are near our throughput limit for serially landing them, so we frequently "rollup" multiple branches into one PR....
Currently it works as follows: 1. Mark the commits to be merged together as `rollup`. (e.g. `r+ rollup`) These commits will have an implicit priority of `-1` to postpone the...
[The code](https://github.com/basho/riak_kv/pull/914) specifically matches on '@username: retry'. The colon shouldn't be necessary. And it should allow you to retry on the pull-request itself with a sha: '@username retry deadbeef'.
It is sometimes hard to backtrack from the comments that bors leaves on a github commit over to the original Pull Request that prompted bors to attempt a merge. It...
Often PRs come through where one can be highly confident, or even certain, that the PR will not cause test failure. (e.g. documentation that is not tested, typos in comments,...
We often end up noticing that bors has been sitting silently after claiming to be testing some new PR; it turns out that if the commit author doesn't match the...
Rust's bors instance is close to the API rate limit (though I don't have numbers), and already doesn't update fast enough, with a 5 minute polling interval. This situation impresses...
When using the status API, bors doesn't do any counting of successes. If the number of successes is greater than zero and it sees no failures, it will assume it...
Reading through the code, the approval list has several issues: - `r=me` on a commit will put both the posting user and a username "me" on the approval list -...
Currently there's a two-step process for merging a successful PR: see that the tests passed and post the status to github; see that the branch is ready for merge and...