potiuk opened a new pull request, #24763:
URL: https://github.com/apache/airflow/pull/24763

   The "provider_dependencies.json" file gets automatically generated
   by pre-commit and in case it cannot be json-parsed, it will break
   building the CI image. This is a bit chicken-egg because on
   CI the image is needed to run pre-commits that could warn the
   user this is the case (and the image fails build with a bit
   cryptic message).
   
   This PR improves the diagnostics:
   
   * it runs the pre-commit check before image building which will
     fix the generated file (and will let the build run - only to
     fail at the latest static-checks step
   
   * it prints warning to the user seeing pre-commit error to not
     modify the file manually but let pre-commit do the job.
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in a 
newsfragement file, named `{pr_number}.significant.rst`, in 
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to