highfive
highfive copied to clipboard
servo
Github hooks to provide an encouraging atmosphere for new contributors
Despite the changes in #75 I still had to remove it manually in https://github.com/servo/servo/pull/10225.
This is actually an upstream repository that gets updated occasionally, so any changes made to it should also be made in the [original repository](https://github.com/w3c/wptrunner).
Specifically, it's easy to write `disable: whatever` instead of the correct `disabled: whatever`. Also, we could check for an issue number or URL in the disabling message.
We don't run highfive on rust-mozjs yet, but this is one of those dangerous constructs that it would be nice to warn about.
A lot of refactoring took place, mostly moving code into classes and removing existing tests in favor of using python's unittest module. I still need to determine a way to...
Saying "please consider add a reftest" is useless if the PR author has no idea what a reftest is.
Sometimes PRs get r+'d without Travis CI finishing its build, which causes homu to fail when the PR fails tidy. It may be beneficial when the contributor pushes a new...
The first time the label is added, we should check for the presence of common issues. I need to think about what this involves, but off the top of my...
This would enable a "merge if this compiles" workflow which allows reviewers to be more hands-off during the process.