Skip to content

ci: run required checks on merge_group for the merge queue - #536

Merged
ScriptedAlchemy merged 5 commits into
mainfrom
ci/merge-group-triggers
Sep 4, 2026
Merged

ci: run required checks on merge_group for the merge queue#536
ScriptedAlchemy merged 5 commits into
mainfrom
ci/merge-group-triggers

Conversation

@ScriptedAlchemy

@ScriptedAlchemy ScriptedAlchemy commented Sep 4, 2026

Copy link
Copy Markdown
Owner

Summary

Adds a merge_group: (branches: main) trigger to every workflow that provides a required check on mainci.yml (Verify, Examples check, Release gates, Host install proofs), docs.yml (Docs site), and changeset.yml (Changeset present) — so a GitHub merge queue can gate on them.

Context: twice today individually-green PRs broke main when combined (#486×#490, #518×#509). GitHub's merge queue is the fix, but it is only offered to organization-owned repositories: creating a merge_queue ruleset on this user-owned repo returns 422 Invalid rule 'merge_queue'. As the fallback, classic branch protection on main now requires the six checks above and an up-to-date branch (required_status_checks.strict: true). The merge_group triggers are therefore dormant, documented as such in each workflow, and make queue adoption a single ruleset away once the repository moves to an organization.

Details

  • ci.yml: merge_group trigger; Verify runs the Node 24 leg for queue entries (the required context is Verify (Node 24)), the full matrix still runs on every main push. The changes job stays PR-only, so queue entries never skip heavy jobs (same as main pushes). Concurrency is SHA-keyed with no cancellation for queue entries.
  • docs.yml: merge_group trigger; build only, deploy steps remain gated on push/dispatch of main.
  • changeset.yml: merge_group trigger; the queue run reports success without evaluating (a merge_group event carries no PR labels and stacks earlier queue entries). Enforcement remains on the pull request, which must be green to enter the queue. Concurrency group falls back to github.sha when there is no PR number.

Validated with actionlint. CI-only: skip-changeset.

@ScriptedAlchemy ScriptedAlchemy added the skip-changeset PR changes a publishable package but ships no observable change; changeset not required label Sep 4, 2026
@changeset-bot

changeset-bot Bot commented Sep 4, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: df3f51a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@ScriptedAlchemy
ScriptedAlchemy enabled auto-merge (squash) September 4, 2026 06:31
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 4, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-04T06:34:37.744329Z 274cbee PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@pkg-pr-new

pkg-pr-new Bot commented Sep 4, 2026

Copy link
Copy Markdown
npm i https://pkg.pr.new/ScriptedAlchemy/agent-bundle@536
npm i https://pkg.pr.new/ScriptedAlchemy/agent-bundle/create-agent-bundle@536
npm i https://pkg.pr.new/ScriptedAlchemy/agent-bundle/@agent-bundle/runtime@536

commit: df3f51a

@ScriptedAlchemy
ScriptedAlchemy merged commit dacb5b0 into main Sep 4, 2026
20 of 21 checks passed
@ScriptedAlchemy
ScriptedAlchemy deleted the ci/merge-group-triggers branch September 4, 2026 09:01
ScriptedAlchemy added a commit that referenced this pull request Sep 5, 2026
…ue readiness audit (#557)

The Verify matrix comment in ci.yml still named "Verify (Node 24)" as the
required check on main; #549 replaced it with the static "Verify gate" job.
Audit of every required-check workflow for merge_group readiness (#536)
found no other gap; findings and the settings commands live in the PR body.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changeset PR changes a publishable package but ships no observable change; changeset not required

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant