ci: run the build on merge_group events

[jamesarich]

Lets a merge queue run the board builds on the group it is about to merge, so the queue can be turned on for master.

Summary by CodeRabbit

• Chores
  • Automated checks now also run for merge queue events. Existing pull request and release triggers remain unchanged. This extends when checks run during change integration; no application features or user-facing behavior have changed.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

🧰 Additional context used

📚 Code guidelines (1)

AGENTS.md — auto-discovered

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 48deecd3-35a4-4d93-827e-8a97a48ae449

📥 Commits

Reviewing files that changed from the base of the PR and between 17f6209 and e6f786e.

📒 Files selected for processing (1)

• .github/workflows/githubci.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The GitHub Actions workflow now runs for merge_group events. Existing pull request and release triggers remain unchanged.

Changes

CI triggers

Layer / File(s)	Summary
Add merge group trigger .github/workflows/githubci.yml	The workflow now runs for merge_group events. Existing pull request and release triggers remain unchanged.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to e6f78

The workflow runs board builds for merge-group events, and this change shows no code-level blocker to merging.

Architecture Summary

Architecture risk: 🔵 Low · up to e6f78

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

• observed — Modified behavior in .github/workflows/githubci.yml: Added merge_group as a workflow trigger.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: running the build for merge_group events.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checked the workflow gate,
“Merge groups may join the queue!”
The old triggers still remain,
While CI wakes for one more cue.
I nibble clover, pleased and bright,
Then hop along beneath the moon.}

_{Comment @coderabbitai help to get the list of available commands.}