Thanks for the feedback! I agree that running the linter before checking the code into version control would be even better (and in fact we have an API that al

Thanks for the feedback! I agree that running the linter before checking the code into version control would be even better (and in fact we have an API that allows that), but our goal with this tool was to interrupt the development workflow as little as possible. Hence checking code in the version control system seemed a reasonable approach. Also, today many teams use a pull-request based workflow, where code does not get merged into the main branch before it is reviewed (Github pull-review integration is coming soon btw). And of course the tool can't fully automate code review (since a linter can never know the intent of the programmer), but it can help you to already weed out many problems before a reviewer looks at the code, thus giving you more time to find the really interesting / dangerous bugs in the code.