On 3/28/14 10:30 AM, Mihai Bivol wrote:
Hello,
I am working on a tool that integrates pylint with github pull
requests[1]. My goal is to make the linting process as less disruptive
as possible and help devs fix issues in their code before submitting
it to review. I saw in another thread that some of you already have
some experience using a linter on introduced code. Before continuing
working on my approach I am curious to see how other approaches worked
and how others introduced this in their team's workflow.
We have a tool that does coverage and pylint measurement on github
submissions:
http://engineering.edx.org/2013/12/diff-cover-test-coverage-for-git-commits/
It's run automatically by our Jenkins CI server, and many developers run
it locally to check on the work they are about to submit.
--Ned.
Thanks,
Mihai
[1] https://github.com/mihaibivol/pylinthub
_______________________________________________
code-quality mailing list
code-quality@python.org
https://mail.python.org/mailman/listinfo/code-quality
_______________________________________________
code-quality mailing list
code-quality@python.org
https://mail.python.org/mailman/listinfo/code-quality
