Run CI on chart and airflow-ctl release-branch pull requests#69626
Merged
Conversation
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496 and
jscheffl
as code owners
Pull requests targeting the chart/v*-test|stable and airflow-ctl/v*-test|stable release branches received no CI at all: those branch patterns were missing from the pull_request/push branch filters of ci-amd, ci-arm and codeql-analysis, so only branch-independent bot checks reported and a PR could show all-green without any tests, static checks, or CodeQL ever running. Add the chart and airflow-ctl release-branch patterns to those triggers (the sync-enforced AMD-only trigger block in check_ci_workflows_in_sync.py is updated in the same change so the amd/arm guard keeps passing). push triggers get the -test variants only, matching the existing release-prep push convention.
potiuk
force-pushed
the
fix-ci-triggers-chart-airflowctl-branches
branch
from
c704f36 to
eb97efd
Compare
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-3-test
kaxil
approved these changes
Jul 8, 2026
gopidesupavan
approved these changes
Jul 8, 2026
Contributor
Backport failed to create: v3-3-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 6d155bb v3-3-testThis should apply the commit to the v3-3-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. |
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
3 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.
PRs targeting the
chart/v*-test|stableandairflow-ctl/v*-test|stablerelease branches received no CI at all — those branch patterns were missing from thepull_request/pushbranch filters ofci-amd,ci-arm, andcodeql-analysis, so only branch-independent bot checks (Mergeable/WIP) reported and a PR could show all-green without any tests, static checks, or CodeQL running (e.g. #69579 againstchart/v1-2x-test).This adds the chart and airflow-ctl release-branch patterns to those triggers. The sync-enforced AMD-only trigger block in
check_ci_workflows_in_sync.pyis updated in the same PR so the amd/arm guard keeps passing;pushtriggers get the-testvariants only, matching the existing release-prep push convention.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines