Scope backport-to-v3-2-test label to PRs targeting main#65386
Merged
Conversation
Uses the per-rule `targetBranchFilter` option added in kaxil/boring-cyborg#112 so the backport label is not applied to PRs opened directly against the v3-2-test maintenance branch — where a backport label is meaningless. Also teaches the `check-boring-cyborg-configuration` prek hook about the new `{paths, targetBranchFilter}` object form for label rules.
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496 and
jscheffl
as code owners
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-2-test
kaxil
approved these changes
Apr 16, 2026
Contributor
Backport failed to create: v3-2-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 9d82363 v3-2-testThis should apply the commit to the v3-2-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
karenbraganz
pushed a commit
to karenbraganz/airflow
that referenced
this pull request
Apr 16, 2026
Uses the per-rule `targetBranchFilter` option added in kaxil/boring-cyborg#112 so the backport label is not applied to PRs opened directly against the v3-2-test maintenance branch — where a backport label is meaningless. Also teaches the `check-boring-cyborg-configuration` prek hook about the new `{paths, targetBranchFilter}` object form for label rules.
3 tasks
potiuk
added a commit
that referenced
this pull request
Apr 26, 2026
…#65872) Backport of the prek-script half of #65386 to fix static checks on v3-2-test after #65610 added a backport-to-airflow-ctl-v0-1-test rule in dict form ({paths, targetBranchFilter}). The legacy script on v3-2-test only understood the flat list-of-globs form, so it flagged `paths` and `targetBranchFilter` as unused glob patterns and failed the check. The .github/boring-cyborg.yml YAML changes from #65386 are intentionally omitted: those targeted the `backport-to-v3-2-test` rule that lives on main, which has no analogue on this branch (here it is `backport-to-v3-1-test` and the existing list form continues to work).
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Apr 26, 2026
Backport of the prek-script half of apache#65386 to fix static checks on v3-2-test after apache#65610 added a backport-to-airflow-ctl-v0-1-test rule in dict form ({paths, targetBranchFilter}). The legacy script on v3-2-test only understood the flat list-of-globs form, so it flagged `paths` and `targetBranchFilter` as unused glob patterns and failed the check. The .github/boring-cyborg.yml YAML changes from apache#65386 are intentionally omitted: those targeted the `backport-to-v3-2-test` rule that lives on main, which has no analogue on this branch (here it is `backport-to-v3-1-test` and the existing list form continues to work).
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 27, 2026
…#65872) Backport of the prek-script half of #65386 to fix static checks on v3-2-test after #65610 added a backport-to-airflow-ctl-v0-1-test rule in dict form ({paths, targetBranchFilter}). The legacy script on v3-2-test only understood the flat list-of-globs form, so it flagged `paths` and `targetBranchFilter` as unused glob patterns and failed the check. The .github/boring-cyborg.yml YAML changes from #65386 are intentionally omitted: those targeted the `backport-to-v3-2-test` rule that lives on main, which has no analogue on this branch (here it is `backport-to-v3-1-test` and the existing list form continues to work).
vatsrahul1001
pushed a commit
that referenced
this pull request
May 20, 2026
…#65872) Backport of the prek-script half of #65386 to fix static checks on v3-2-test after #65610 added a backport-to-airflow-ctl-v0-1-test rule in dict form ({paths, targetBranchFilter}). The legacy script on v3-2-test only understood the flat list-of-globs form, so it flagged `paths` and `targetBranchFilter` as unused glob patterns and failed the check. The .github/boring-cyborg.yml YAML changes from #65386 are intentionally omitted: those targeted the `backport-to-v3-2-test` rule that lives on main, which has no analogue on this branch (here it is `backport-to-v3-1-test` and the existing list form continues to work).
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
2 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.
Uses the per-rule
targetBranchFilteradded in kaxil/boring-cyborg#112 so thebackport-to-v3-2-testlabel is only applied to PRs whose base branch ismain. A PR opened directly againstv3-2-testdoes not need a backport label for itself.Also teaches the
check-boring-cyborg-configurationprek hook about the new{paths, targetBranchFilter}object form for label rules so it no longer treats those keys as unused patterns.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.6) following the guidelines