Merged
Conversation
When we merge to v3-2-test it usually triggers full build, however when there is only an .md file change (which happens for AGENTS.md updates for example) - it should not trigger the complete rebuild.
a3bc979 to
8b0bdf0
Compare
bugraoz93
approved these changes
Apr 13, 2026
github-actions bot
pushed a commit
that referenced
this pull request
Apr 13, 2026
When we merge to v3-2-test it usually triggers full build, however when there is only an .md file change (which happens for AGENTS.md updates for example) - it should not trigger the complete rebuild. (cherry picked from commit c8ebd28) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Contributor
Backport successfully created: v3-2-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
potiuk
added a commit
that referenced
this pull request
Apr 13, 2026
When we merge to v3-2-test it usually triggers full build, however when there is only an .md file change (which happens for AGENTS.md updates for example) - it should not trigger the complete rebuild. (cherry picked from commit c8ebd28) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
When we merge to v3-2-test it usually triggers full build, however when there is only an .md file change (which happens for AGENTS.md updates for example) - it should not trigger the complete rebuild. (cherry picked from commit c8ebd28) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
When we merge to v3-2-test it usually triggers full build, however when there is only an .md file change (which happens for AGENTS.md updates for example) - it should not trigger the complete rebuild. (cherry picked from commit c8ebd28) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
When we merge to v3-2-test it usually triggers full build, however when there is only an .md file change (which happens for AGENTS.md updates for example) - it should not trigger the complete rebuild. (cherry picked from commit c8ebd28) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
When we merge to v3-2-test it usually triggers full build, however when there is only an .md file change (which happens for AGENTS.md updates for example) - it should not trigger the complete rebuild. (cherry picked from commit c8ebd28) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When we merge to v3-2-test it usually triggers full build, however
when there is only an .md file change (which happens for
AGENTS.md updates for example) - it should not trigger the
complete rebuild.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.