-
Notifications
You must be signed in to change notification settings - Fork 14.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allowing short package names in build-docs breeze command #34004
Conversation
We need also to update README_RELEASE_PROVIDER_PACKAGES.md airflow/dev/README_RELEASE_PROVIDER_PACKAGES.md Lines 362 to 366 in ffc9854
|
@eladkal @potiuk with the current changes, we have not retired the older
It takes combination of args + option from package-filter together! |
1ae2e03
to
a0903ec
Compare
One small thing also to add: Line 92 in 0d93cc5
--package-filter .
There is also a follow-up after that one, but it should be a separate PR. We should adapt the current CI/selective checks to use the list of short package ids rather than |
@potiuk Made the changes. Can you take a look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Random error. Merging. |
Introducing short_version flag so that the users who build docs can now provide a short hand name instead of the whole name while building the docs for specific packages.
Some examples:
Selecting two packages - cncf kubernetes and airbyte using short hand
closes: #33876
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.