potiuk opened a new pull request #21643: URL: https://github.com/apache/airflow/pull/21643
The wrapper scripts in static checks were remnant of old approach of running the static checks. They were there for those who did not want to use pre-commit and they provided extra parameters that could be passed and variables that could be used and provided more verbose output. This is however all possible with the `pre-commit` command and we are all used to run pre-commit and we even have missing auto-complete for those in Breeze so there is no need to keep the wrappers around. The static-checks folder remains now only for the real "static check" actions that are run directly from CI: * running all static checks * running only basic static checks * running www lint * running ui lint Those scripts are directly referred from the ci.yml worflow, thus the "scripts/ci/static-checks" is now back to what it was orignally used for. <!-- 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 [UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md). -- 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]
