31–35 of 35 posts
It runs on the commit diff with a specified linting tool (used it with pep8 and jshint), it is also fairly easy to add new linters.
Here's a fork that works nicely with Travis: https://github.com/glowdigitalmedia/imhotep
This looks pretty awesome and will just get better as more languages get supported. But, it comments on commits, not on the diff in the PR. I think commeting on the diff looks nicer (you see code snippet with the comment) and in my opinion it's also easyer to find all the comments that way. Instead of clicking the commit hash on the commen each time.
Instead of using a service like this one (or Hound) that comments directly on pull requests, we chose to integrate the same tools in our build process with Phare ( https://github.com/mirego/phare ), a command-line tool we built which runs Rubocop, JSHint, JSCS, etc. and exits with a global status. If the code has coding style violations, the build breaks. Exactly like it would if we pushed a failing test. Personally,…
Are there any opensource tools that do the same thing( like reek for ruby) ? I would like to use something like this at work but we don't host code on github.