benboeser

+1 on Piotrs comment (disclosure: founding team of ReviewNinja - http://review.ninja). We also found that most users like to put some more structure around their code review and appreciate the fact that tools like the ones mentioned by Piotr give more visibility into outstanding issues that need to be closed, before a pull request can be merged. It is also helpful for most to get a better handling around who 'approved' (+1ed) a PR.

The http://review.ninja/auth/github is a very old version of the tool (1 month old). The team will cut over to master next Tuesday