Flag airflow-ctl release-branch sync PRs for backport-to-v0-1-test attention - #71224
Draft
Lee-W wants to merge 1 commit into
Draft
Flag airflow-ctl release-branch sync PRs for backport-to-v0-1-test attention#71224Lee-W wants to merge 1 commit into
Lee-W wants to merge 1 commit into
Conversation
…tention The backport-to-airflow-ctl/v0-1-test label only fired for PRs targeting main. The main->v0-1-test and v0-1-test->v0-1-stable sync PRs target the release branches directly, so they never got flagged even though that is exactly where branch-specific paths (e.g. airflow-ctl/.pre-commit-config.yaml pointing at a script that only exists on one branch) have silently drifted before, causing apache#71096.
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-3-test
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
1 participant
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.
The
backport-to-airflow-ctl/v0-1-testlabel only fired for PRs targeting main. Themain->v0-1-testandv0-1-test->v0-1-stablesync PRs target the release branches directly, so they never got flagged even though that is exactly where branch-specific paths (e.g.airflow-ctl/.pre-commit-config.yamlpointing at a script that only exists on one branch) have silently drifted before, causing #71096.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.