[
https://issues.apache.org/jira/browse/ARROW-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619734#comment-16619734
]
Antoine Pitrou commented on ARROW-3260:
---------------------------------------
I don't think, I think it would be nice to be able to treat linting as a last
polish step when a PR is ready, not as something you must do each time you push
a new change to the CI (you may automate linting in a commit hook but you still
have to fix lint errors manually).
> [CI] Make linting a separate job
> --------------------------------
>
> Key: ARROW-3260
> URL: https://issues.apache.org/jira/browse/ARROW-3260
> Project: Apache Arrow
> Issue Type: Wish
> Components: C++, Continuous Integration, Python
> Reporter: Antoine Pitrou
> Priority: Major
>
> When pushing changes I get routinely frustrated because Travis-CI fails early
> on a linting failure. It would be nice if linting (Python, C++) was a
> separate job so as not to disrupt the development workflow so much.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
