4 ms·
This is also useful as a demonstration of how the Servo developers use bots to augment the review of pull requests. See also "bors", the Rust compiler's continu
by kibwen 12y ago
This is also useful as a demonstration of how the Servo developers use bots to augment the review of pull requests. See also "bors", the Rust compiler's continuous integration bot: http://buildbot.rust-lang.org/bors/bors.html http://buildbot.rust-lang.org/bors/bors.html
It would be very interesting to survey the largest projects being developed on Github to determine if they've also grown bespoke ways of dealing with the platform's pain points. I know that the Rust developers aren't entirely satisfied with the tools that Github provides (which seem to be optimized for small projects at the expense of large ones), but Github's network effects are just too good to ignore for a project that relies on volunteer contributions.
- kodablah 12y agoI have seen many projects have little bots do things like post to third-party review services or whatever. Many projects use CI tools that have GitHub integration (e.g. travis), Rust's is just rolling their own so they needed their own GitHub integration. We should be lauding GitHub for their willingness to support integration, even if their native tools are a tad lacking.
- masklinn 12y agoAFAIK Bors doesn't use any github integration, it behaves as a user (and I'm pretty sure its messages are too complex to go through the statuses API and result in anything other than unreadable garbage)
- dbaupp 12y agoBors does have some github integration and it will automatically merge pull requests and I believe it does update the status, but yes, the details of its interactions are by posting normal comments.
- masklinn 12y ago> which seem to be optimized for small projects at the expense of large ones Definitely, you easily hit its limitations with big projects: * the commits view is completely useless if development is highly branchy (although to be fair that's the case for pretty much all git history visualisation tools) * the CI integration (statuses[0]) is very limited with only 4 states (pending, success, error and failure) and doesn't work OOTB with merged heads * issues-filtering tools have odd cases when you're trying to e.g. filter by multiple tags * and they're not available at all the PR list * the notifications system is insufficient and incomplete (IIRC you're not notified when assigned on an issue or PR…) * the teams integration is lacking (essentially, teams are only very broad ACLs, you can't triage issues to teams so you have to use tags, except when you start doing complex queries involving multiple tags it all breaks down) [0] https://developer.github.com/v3/repos/statuses/ https://developer.github.com/v3/repos/statuses/