Skip to content

feat(ci): introduce merge queue#2024

Open
elezar wants to merge 1 commit into
mainfrom
feat/1946-merge-queue/elezar
Open

feat(ci): introduce merge queue#2024
elezar wants to merge 1 commit into
mainfrom
feat/1946-merge-queue/elezar

Conversation

@elezar

@elezar elezar commented Jun 26, 2026

Copy link
Copy Markdown
Member

🏗️ build-from-issue-agent

Summary

Add merge-queue support for the required OpenShell CI gates. The existing copy-pr-bot PR mirror flow remains intact, and merge-group runs publish the same stable OpenShell / ... status contexts for the queued integration SHA.

Related Issue

Closes #1946

Changes

  • .github/workflows/branch-checks.yml: add merge_group as a required branch-check trigger.
  • .github/workflows/branch-e2e.yml: add merge_group and make push, manual, and queue E2E selection explicit.
  • .github/workflows/helm-lint.yml: add merge_group validation for queued integration commits.
  • .github/workflows/required-ci-gates.yml: publish required CI statuses for merge-group SHAs without requiring a pull-request/<N> mirror branch.
  • .github/actions/pr-gate/action.yml: document that non-push events include merge_group.
  • CI.md and architecture/build.md: document the maintainer merge-queue workflow and required contexts.

Deviations from Plan

None — implemented as planned. The branch was rebased after #2022 merged so local validation includes that main Rust test fix.

Testing

  • YAML parse for touched workflow/action files
  • mise run markdown:lint
  • git diff --check origin/main...HEAD
  • mise run pre-commit passes locally (attempted after rebasing on fix(server): update driver spec test argument #2022; Rust check/lint, Python, Helm, Markdown, license, docs, and packaging checks passed, but test:rust still fails on this machine because xcrun --show-sdk-path cannot find the macOS SDK and the CLI integration test temporary fake-forward-process cannot link -lSystem)

Tests added:

  • Unit: N/A — workflow YAML and docs only.
  • Integration: N/A — no application integration paths changed.
  • E2E: N/A — no e2e/ files changed.

Checklist

  • Follows Conventional Commits
  • Commits are signed off (DCO)

Documentation updated:

  • CI.md: merge queue behavior, required contexts, maintainer workflow, and workflow file roles.
  • architecture/build.md: CI architecture now includes merge-group validation.

Closes #1946

Signed-off-by: Evan Lezar <elezar@nvidia.com>
@elezar elezar requested a review from mrunalp as a code owner June 26, 2026 14:23
@elezar elezar added the area:build Related to CI/CD and builds label Jun 26, 2026
@elezar elezar requested review from a team, derekwaynecarr and maxamillion as code owners June 26, 2026 14:23
@elezar elezar added the area:build Related to CI/CD and builds label Jun 26, 2026
Comment on lines +58 to +61
*)
echo "::error::Unsupported event '$EVENT_NAME'" >&2
exit 1
;;

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: Why not just default to the values for workflow_dispatch (which is what this code was doing beforehand).

Comment on lines +49 to +51
run_core_e2e=true
run_gpu_e2e=true
run_kubernetes_ha_e2e=false

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should rather not run e2e tests in the merge queue -- or use the same logic as we do for PRs?

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

Labels

area:build Related to CI/CD and builds

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(ci): introduce merge queue for main

1 participant