PullApprove + GitHub Code Review
As most of our users know, GitHub recently added some new features around code review (as well as a bunch of other cool things). We’ve been asked many times…
“What does this mean for PullApprove?”
If you’ve taken a look at both, you’ll immediately see the similarities. GitHub code review now offers a subset of PullApprove’s features. At the moment, it simply allows you to require 1 approval (from someone other than the author) for the PR to pass. The review process within GitHub has been updated to support this flow, and if that’s all you need then by all means, go use it! While we believe this is a great start, and they’re certainly going to build on it over time, for users with even slightly more complex workflows it just simply doesn’t cut it.
Why use PullApprove?
PullApprove always has been, and will continue to be, the tool for teams who want to implement a more sophisticated code review process. Our goal is to be the go-to solution for anyone who needs more control over their process, but does not want to build and manage their own internal integration. PullApprove’s simple, yet powerful set of features is here to help you ensure that your code is meeting the standards you’ve set.
So, I’d like to announce our next step towards this.
After months of listening to and processing the feedback of our users, we’ve taken everything we’ve heard and redesigned how you can structure your code reviews. The result is .pullapprove.yml `version: 2` — a slight variation in the .pullapprove.yml layout, with a huge gain in flexibility. Now, all the PullApprove settings you know and love can be applied on a per-group basis — meaning that each group can have a different `approve_regex` and you can give your “code review” and “security review” independently. We’ve also implemented a number of features that people have been asking for, and believe we’re now much better suited to continue doing so.
But…will they work together?
As is usually the case with new GitHub features, an API is not available right away. So in terms of true “integration”, we simply have to wait. That being said, we’ve been in conversation with GitHub and believe there’s going to be a great opportunity to tie-in to the now-native approval process.
GitHub is a great platform, and we’re happy to be a part of it. By building more code review features into their product, they’ve validated the importance of code review and educated more people than any other service possible could. As a broad and diverse platform, they can’t (and shouldn’t) build everything — and that’s why we’re here.