Skip to content

[CI] Run pr-test + pr-test-extra on PRs targeting release/v0.5.12 - #26090

Closed
Kangyan-Zhou wants to merge 1 commit into
release/v0.5.12from
enable-pr-test-on-release-v0.5.12
Closed

Kangyan-Zhou wants to merge 1 commit into
release/v0.5.12from
enable-pr-test-on-release-v0.5.12

Conversation

@Kangyan-Zhou

@Kangyan-Zhou Kangyan-Zhou commented May 22, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Adds release/v0.5.12 to the pull_request.branches: filter on both pr-test.yml and pr-test-extra.yml so PRs targeting the release branch (including the auto-opened cherry-pick PRs) get the same per-commit CI coverage that main-targeted PRs get.

Two-line diff, one branch added in each file. pr-test-extra's run-ci-extra label gate on pull_request events is unchanged.

Why not snapshot the workflows from main

A previous attempt (#26081, closed) tried to snapshot the full set of pr-test workflow files from main to also pick up the scheduling and labelling fixes. Code review caught that the stage-* → base-* rename in #25420 has a wide blast radius across scripts/ci/utils/compute_partitions.py, scripts/ci/utils/slash_command_handler.py, test/run_suite.py, ~200 register_*_ci(suite=...) call sites, and three sibling reusable workflows — landing the snapshot without the rest would break every per-commit job on the release branch.

This PR is therefore scoped to the only thing actually needed for release-branch CI to fire: the trigger filter.

Test plan

🤖 Generated with Claude Code


CI States

Latest PR Test (Base): ❌ Run #26279648646
Latest PR Test (Extra): ❌ Blocked -- run-ci is required first.

Adds release/v0.5.12 to the pull_request branches: filter on both
pr-test.yml and pr-test-extra.yml so that PRs (including auto-opened
cherry-pick PRs) targeting the release branch get the same per-commit
CI coverage as main-targeted PRs.

pr-test-extra continues to require the `run-ci-extra` label on
pull_request events — that gate is unchanged.

This is the minimal change to enable release-branch PR testing; the
broader sync of pr-test workflow logic from main (the stage-* -> base-*
rename and follow-up scheduling fixes) is intentionally deferred,
since that rename has a much wider blast radius across compute_partitions.py,
run_suite.py, and ~200 register_*_ci(suite=...) call sites that would
all need to land coherently.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@Kangyan-Zhou

Copy link
Copy Markdown
Collaborator Author

Closing — superseded by the workflow_dispatch approach. Release-branch verification is handled by manually dispatching pr-test.yml + pr-test-extra.yml against release/v0.5.12 with run_all_tests=true, which doesn't need the pull_request branches: filter extended. Deleting branch on cleanup.

@Kangyan-Zhou
Kangyan-Zhou deleted the enable-pr-test-on-release-v0.5.12 branch May 22, 2026 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant