You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2019/06/02 14:55:14 UTC

[GitHub] [airflow] potiuk commented on issue #5238: [AIRFLOW-4364] Add Pylint to CI

potiuk commented on issue #5238: [AIRFLOW-4364] Add Pylint to CI
URL: https://github.com/apache/airflow/pull/5238#issuecomment-498038230
 
 
   Yeah. Also I it should be possible to disable some rules in parts of the files in case we find it non-compliant and there is a good reason for it. It's one of the valid ways of dealing with such issues.
   
   Also that made me think @BasPH -> I thought maybe we should also have a very short explanation in CONTRIBUTING.md  on the Pylint process we are going to follow - once we create JIRA issues. We could link to the JIRA issue and some links to pylint docs explaining how to deal with checks in case there is no easy fix (mainly #pylint disable/enable comments), because not everyone realises that.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services