Hi Tim / all,

I've been running a "linting as a service" for a while now called Landscape 
- https://landscape.io . It runs pep8, pyflakes and mccabe as well as 
pylint and some other things (such as pyroma and pep257 optionally). You 
then get a report of the errors found as well as diffs since the last 
commit. It might be what you're looking for.

It will create comments on PRs but does not yet use the GitHub status API; 
this is because the GitHub OAuth scopes required to do so are a bit 
generous and put off some people. I'm trying to figure out the best way to 
do that, as I want to keep it as read-only as possible.

I'm also happy to add features and work to make it work better for Django, 
feedback is always good. 

Any questions, fire away!

Carl


PS: Some example pages:
* Project overview: https://landscape.io/github/landscapeio/prospector
* Changes for a particular commit (or PR): 
https://landscape.io/github/spotify/luigi/79/diff
* Comment on PRs: 
https://github.com/mozilla/treeherder-service/pull/343#issuecomment-71704436

On Thursday, January 29, 2015 at 2:18:16 PM UTC+1, Tim Graham wrote:
>
> As a code reviewer, I've really appreciated that we've cleaned up the code 
> using flake8 and have automated "enforcement" via the CI server. I'd like 
> to extend the idea to apply to standardizing import ordering using isort 
> [1]. This mail is to advise everyone of the change and to address any 
> concerns.
>
> Documentation:
> https://github.com/django/django/pull/4008
>
> Automated cleanups:
> https://github.com/django/django/pull/4009
>
> On a related note, the UI for flake8 errors isn't currently very good (you 
> have to look at the bottom of the Jenkins build logs). I'd like to improve 
> that by using a separate service that uses the GitHub status API [2] so 
> that the check can run separately from the tests build. I don't want to 
> reinvent the wheel though, so if there is an existing service we can use 
> for this, great. I'd like to also add checks for documentation build and 
> spelling errors, as well as isort checks (assuming adoption per above).
>
> [1] https://github.com/timothycrosley/isort#readme
> [2] 
> https://github.com/blog/1935-see-results-from-all-pull-request-status-checks
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/74ca3ec2-2c76-4cc9-ae87-b6d1f1204a24%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to