potiuk opened a new pull request, #23193: URL: https://github.com/apache/airflow/pull/23193
Experimentally we've separated some CI-only tools like freespace and find-newer-dependencies as separate scripts (similarly to initialize-virtualenv) but contrary to the initialize, our tools can and should be run in Breeze's virtualenv. However we are just in the middle of using breeze commands in the CI context, the commands are not "alien" any more and they seem to fit the same pattern as other commands. Since we now have the possibility of grouping sub-commmands in separate logical groups, it makes perfect sense to bring the tools to the breeze's sub-commands - mostly because of the auto-complete support and familiarity of using breeze commands in CI. This PR brings both freespace and find-newer-dependencies tools already used in CI to become breeze sub-commands. <!-- 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]
