highfive
highfive copied to clipboard
rust-lang
Github hooks to provide an encouraging atmosphere for new contributors
politely suggest something more descriptive than "typo"
It would be nice if highfive could automatically attach labels to issues that clearly mention what they’re related to in their title. So an issue titled something like ‘rustdoc: foobars...
Is this correct behavior? It seems incorrect, since landing code in any branch of a repo implies knowing how to contribute. #### Example: rust-www was formerly on GitHub pages, so...
E.g. everyone who commented [here](https://github.com/rust-lang/rust/issues/17152) is cc'd [here](https://github.com/rust-lang/rfcs/issues/759). This should also be done for all issue that have already been moved.
We could do this ourselves fairly easily, though at the expense of adding some state. Or we could bounce off a dedicated irc bot.
This project was originally a fork of jdm/highfive, used for Servo. I removed a few things, changed a few things, and since then we've added a lot. It would be...
We currently look for `r? @foo` in messages, but people often write `r? foo`. We should check for this and assign a reviewer for it (ignoring `r?` without a reviewer...
highfive should ping reviewers who forget about a review, probably by leaving a GitHub comment and by an irc ping. I'm not sure exactly how this should work. We could...
Highfive could probably detect changes that mostly change lines that start with `///` and set @steveklabnik as the reviewer.