Adds a merge_group: trigger to ci.yml so the existing CI jobs (and the CI passed aggregating gate) run on the merge-queue group ref. Prerequisite for enabling a required merge queue on main, which auto-updates + tests + merges armed PRs in order (no manual branch updates).
No job logic changed — only the trigger. This is a workflow-trigger-only change that can't be meaningfully validated except by using it, so it is admin-merged past the status checks intentionally (running the full ~20-min E2E matrix on a YAML trigger edit adds no signal).
Adds a `merge_group:` trigger to `ci.yml` so the existing CI jobs (and the `CI passed` aggregating gate) run on the merge-queue group ref. Prerequisite for enabling a required merge queue on `main`, which auto-updates + tests + merges armed PRs in order (no manual branch updates).
No job logic changed — only the trigger. This is a workflow-trigger-only change that can't be meaningfully validated except by using it, so it is **admin-merged past the status checks** intentionally (running the full ~20-min E2E matrix on a YAML trigger edit adds no signal).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds a
merge_group:trigger toci.ymlso the existing CI jobs (and theCI passedaggregating gate) run on the merge-queue group ref. Prerequisite for enabling a required merge queue onmain, which auto-updates + tests + merges armed PRs in order (no manual branch updates).No job logic changed — only the trigger. This is a workflow-trigger-only change that can't be meaningfully validated except by using it, so it is admin-merged past the status checks intentionally (running the full ~20-min E2E matrix on a YAML trigger edit adds no signal).
🤖 Generated with Claude Code