When comparing GitHub Pull Requests vs Gerrit, the Slant community recommends GitHub Pull Requests for most people. In the question“What are the best peer code review tools for small development teams?” GitHub Pull Requests is ranked 1st while Gerrit is ranked 3rd.
Ranked in these QuestionsQuestion Ranking
Pro Already integrated with GitHub projects
Pro Can reference issue numbers and commits in comments
Because GitHub pull requests are integrated with the rest of GitHub, you can reference parts of your git history in comments. This can be handy if you want to point someone to the historical significance of a piece of code.
Pro Free for Public/Open Source Projects
Pro Authorizations for users and groups
Gerrit supports group and user authorizations for various repositories. Only authorized users can push code to the master branch.
Pro Integration with LDAP, bug-tracking tools, CI, etc.
Full integration with LDAP (users, groups), bug-tracking systems (Jira, Bugzilla), CI (Jenkins, Hudson) and other tools.
Pro Configurable project workflow, not always feature branches are the most suitable workflow
Pro Project policy customization can be done with hooks and plugins
Multiple hooks available on various events. Plugin API for more customization of project behavior.
Pro Self-contained installation of Java package, simple upgrades
Most upgrades require only download of new war file and running it in init mode. In some rare cases db reindex is required.
Pro Web UI extension with plugins
A number of plugins available for web UI extension. Plugin API for more customization.
Con No "acknowledgment" or "mark as reviewed"
The code review process should enforce the code to be reviewed by one or two peers at least to be "accepted" or "reviewed". On github, there is no such thing : no way to be sure that a PR has been reviewed by a certain number of reviewers.
Con Not free for non-open source code
Con The UI is very cluttered
Gerrit's user interface is very cluttered and messy, and quite ugly to look at. The navigations is also not very intuitive, which may hold some people off.
Con Difficult to customize
Fixing the UI/UX problems with CSS customization is nearly impossible. The markup doesn't include many classes, making it difficult to target CSS rules to specific elements of the interface.