potiuk commented on issue #25209:
URL: https://github.com/apache/airflow/issues/25209#issuecomment-1191915218

   @vitaly-krugl - if you would like to propose some guidelines - feel free to 
make PR. Like everything else in Airflow.,
   
   Airflow is created by > 2100 contributors and if you would lilke to 
contribute such README and guidelines. That's cool. Seems your experience and 
ideas and cool and it's the best you ca do to help the community to contribute 
a PR with such quidelines.
   
   Also I would lilke to draw your attention, to the fact that we tend not only 
to raise problems when we notice them, and document them in READMES but also 
automate most of such checks. So if you are able to come up with a proposal on 
how to automate such checks and fail PRs that introduce bad practices, adding a 
pre-commit that performs such checks is ideal. We have already ~ 100 
pre-commits like this, so you are most welcome to devlop and submit pre-commit 
that performs such checks. That would be fantastic contribution.
   
   BTW. Converting this into discussion - this is not a bug "per se" in 
airflow. It's the usual (we had probably hundreds of them) discussions on how 
we can improve our dev environment - and usually each such discussion ended up 
as a PR from those who raised it, rather than "bug" issue.
   


-- 
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.

To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to