homu
homu copied to clipboard
servo
A bot that integrates with GitHub and your favorite continuous integration service
Github webhook notifications sometimes get dropped, which can mean that homu is unaware of recent changes. We have [an assertion to guard against that](https://github.com/servo/homu/blob/d2b0d20a379cdf5f70b1cfd78f679c24b123cad4/homu/main.py#L1000), however that just causes silent failure....
This causes multiple builds to be started but only the most recent one matters. The older duplicate ones are ignored but still consume resources.
For any repositories that want to use homu with the travisci github app, https://blog.travis-ci.com/2018-09-27-deprecating-github-commit-status-api-for-github-apps-managed-repositories means that they will not be able to.
As @asajeffrey mentioned in https://github.com/servo/servo/pull/22094#issuecomment-436371106, maybe `homu` can block merging if the `S-needs-squash` exists.
Could we have Homu respond to GitHub's [review](https://help.github.com/articles/about-pull-request-reviews/) [feature](https://blog.github.com/2016-12-07-introducing-review-requests/), as well as `r+`? The event is called [`PullRequestReviewEvent`](https://developer.github.com/v3/activity/events/types/#pullrequestreviewevent).
I was left scratching my head when homu stopped making any progress while there was still an ongoing queue of approved PRs. It turns out in https://github.com/servo/servo/pull/21586 that I had...
Updating to latest homu, we're now seeing a traceback on this line about missing `max_priority`: https://github.com/servo/homu/blob/68e4dd921067b8f22f38439b2f5cec9c23ffc961/homu/action.py#L120 Adding the following k-v under `github` the way the sample config has it: ```toml...
It's common to use delegate+ in a PR, then have the PR author use r+ instead of r=delegator. We should just rewrite that behind the scenes.
Repro steps: 1. `r+` a PR 2. Wait for it to enter the "⏳ Testing commit" (pending) phase 3. `r-` it before the test completes Expected behavior: * The test...
