The problem with pull requests / code reviews
philfreo.com
philfreo.com
Also, Evan Priestly (the lead contributor) responds immediately to any sort of issue and the source is readable. My workplace hosts our own, but I think there may be a hosted version available, too.
It's just an awesome experience using it, and huge thanks to Evan Priestly for creating it.
There are really a lot of additional modules (internal blogs, pastebin, images directory, polls and recently a web layout review tool) that are not really needed in a "traditional" setting, but the base functionalities are there and the tool can be adapted to different workflows. So, if someone is evaluating alternatives for an internal infrastructure, i'd give it a try.
Edit: And in such "traditional" workplace, you'll likely need the option 'phabricator.serious-business' => true in your config file (it replaces button names with saner alternatives).
[1] https://github.com/danielribeiro/github-diff-highlight#githu...
It has a much better view of the diff, incorporating much more context and a side-by-side view (here is a example change I just randomly pulled from rietveld's internal rietveld: https://codereview.appspot.com/8726052/diff/1/pom.xml). It also has the ability to group multiple in-line comments together in chunks, so it is apparent to coworkers when one round of the code review is done and they should work on it and get it back to you. It also has tons of other great features (email integration, keyboard shortcuts for moving around the code, etc etc).
Of course, you can only use this if you control a project, and you will have to do a little integration work, but if code review is an important part of your team's workflow, I highly recommend the investment.