If the code has coding style violations, the build breaks. Exactly like it would if we pushed a failing test.
Personally, I’m not a fan of the noise generated by comments about coding style on pull requests.
There's a balance to be found between core checks that run at build time, and additional, more extensive checks, which run automatically and asynchronously (!) once a developer believes their changes to be good enough. Both things have their place in a proper software development flow.
If you also add "and any coding style things you care about, you have to make the linter check for", then you don't have to waste any time on that stuff in the pull request.
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
What's your plan on this? I'd like to use it for our private repositories.
Edit: My web hooks are returning errors. I'll submit some feedback.
Edit: Nevermind, I found the support form.
https://houndci.com/ http://scrutinizer-ci.com/ http://landscape.io/ http://codeclimate.com/
I would like to use something like this at work but we don't host code on github.
In Python this usually means running flake8 as a Travis job.
1: https://github.com/blog/1935-see-results-from-all-pull-reque...