Skip to content

ci: prepare workflows for GitHub merge queue - #2779

Closed
serrrfirat wants to merge 2 commits into
stagingfrom
issue-2719-pr-a-merge-queue-ready
Closed

serrrfirat wants to merge 2 commits into
stagingfrom
issue-2719-pr-a-merge-queue-ready

Conversation

@serrrfirat

Copy link
Copy Markdown
Collaborator

Summary

  • add merge_group support to the core CI workflows used by PR A
  • remove staging-specific skips and cache-save conditions from test.yml and code_style.yml
  • fire Claude review on active non-draft PRs instead of the old staging-promotion label

Validation

  • parsed the updated workflow YAML locally with PyYAML
  • ran git diff --check
  • did a focused workflow-semantics review on the final diff

Not in this PR

  • deleting staging promotion infrastructure
  • changing regression-test-check.yml for merge_group
  • docker / release-plz / staging branch cleanup

Part of #2719.

@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.

@github-actions github-actions Bot added scope: ci CI/CD workflows size: M 50-199 changed lines risk: medium Business logic, config, or moderate-risk modules contributor: core 20+ merged PRs labels Apr 21, 2026
@serrrfirat
serrrfirat requested a review from henrypark133 April 21, 2026 10:28
@henrypark133

Copy link
Copy Markdown
Collaborator

Closing this as superseded by #3104. The branch strategy changed: main already contains staging, so the replacement PR handles the main-only workflow cutover directly instead of preparing staging for a later promotion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contributor: core 20+ merged PRs risk: medium Business logic, config, or moderate-risk modules scope: ci CI/CD workflows size: M 50-199 changed lines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants