homu
homu copied to clipboard
rust-lang
A bot that integrates with GitHub and your favorite continuous integration service
Bors has a `squash` feature that is also [documented](https://bors.rust-lang.org/), but it doesn't actually work very well for us since rollups do not get squashed. This can easily [cause confusion](https://github.com/rust-lang/rust/pull/99393#issuecomment-1192243497).
There have been two circumstances where a normal `@bors r+` approved an old commit: * https://github.com/rust-lang/rust/pull/95251#issuecomment-1079483432 * https://github.com/rust-lang/rust/pull/98708#issuecomment-1171587241 My hunch is that somehow bors missed the push notification, and the...
There are r+'s that Bors never receives and it has led to #174 but I thought it's best to raise a ticket for the general Webhook reliance The fixes iterated...
I often want to test multiple related changes in PRs that can affect performance and compare the performance effect of these changes. The usual workflow is like this: 1) Commit...
Fixes #136. This only change behaviour for `@bors squash`. With the current implementation, bors will still take credit when configured to keep history linear or do autosquashes.
https://github.com/rust-lang/rust/pull/98864 has a broken render because of a <details> tag in a commit message. The fix is to escape `&` characters.
Tests pass, but that coverage is pretty minimal I think -- not sure, but I think our best bet is to just merge and monitor after doing so to make...
Hey, often with delegates you want to let the user know how they can r+ and that they should use `r=` to approve the PR. An example comment often looks...
After oli-obk changed the assignee and approved at the same time, the below pr still showed as not approved on https://bors.rust-lang.org/queue/rust with the assignee still being yaahc. See https://github.com/rust-lang/rust/pull/90602#issuecomment-1077864002
