"My rule of thumb: If you have more than 10 contributors, at least 4 of which are active daily, it may be worth it to invest in some real infrastructure." Disc

"My rule of thumb: If you have more than 10 contributors, at least 4 of which are active daily, it may be worth it to invest in some real infrastructure." Disclaimer: I'm the creator of GitSense. We are working on a solution to make GitHub pull requests enterprise ready. I do agree that GitHub's pull request model is not quite enterprise ready, but they have a solid foundation that you can build on top of. With their API, were able to build a solution that I believe will address most of its short comings. For example, my first concern with GitHub's pull request system, is it is at the repository level. With Gerrit, you can see requests at the branch level. With our enhancements you'll be able to track pull requests from different repositories at the branch level: http://screenshots.gitsense.com/enterprising-github-pulls.html#pulls-at-branch-level http://screenshots.gitsense.com/enterprising-github-pulls.ht... We are also able to address the concern of dealing with new commits. With our Smart Attributes technology, it is very easy to flag what commits you have reviewed. http://screenshots.gitsense.com/enterprising-github-pulls.html#mark-unreviewed-commits http://screenshots.gitsense.com/enterprising-github-pulls.ht... And then refine the list so you'll only have to deal with the newer commits. http://screenshots.gitsense.com/enterprising-github-pulls.html#refined-commits-list http://screenshots.gitsense.com/enterprising-github-pulls.ht... We also take care of the problem of not having a side by side diff. With our solution, you'll be able to use side by side diffs to review pull requests. http://screenshots.gitsense.com/enterprising-github-pulls.html#side-by-side-diffs http://screenshots.gitsense.com/enterprising-github-pulls.ht...