Improve docs-build selective checks to include RELEASE_NOTES.rst
#49558
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amoghrajesh
requested review from
ashb,
gopidesupavan,
jedcunningham and
potiuk
as code owners
amoghrajesh
changed the title
docs-build selective checks to include RELEASE_NOTES.rst
potiuk
approved these changes
Apr 22, 2025
hussein-awala
approved these changes
Apr 22, 2025
Member
|
Constraints generation fixed in main |
kaxil
pushed a commit
that referenced
this pull request
Apr 23, 2025
) (cherry picked from commit 1bcbe8f)
prabhusneha
pushed a commit
to astronomer/airflow
that referenced
this pull request
Apr 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Saw two occurrences when the selective checks didnt run docs build on two PRs in just two days:
xcom_pullbehaviour to release notes #49455 (fixed later by https://github.com/apache/airflow/pull/49493/files)So it is better to catch this sort of thing by running docs-build on RELEASE_NOTES.rst to avoid any such CI failures.
^ 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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.