Skip to content

Add types: [checks_requested] to merge_group triggers - #55

Merged
nhorton merged 1 commit into
mainfrom
fix/merge-queue-types
Jan 16, 2026
Merged

Add types: [checks_requested] to merge_group triggers#55
nhorton merged 1 commit into
mainfrom
fix/merge-queue-types

Conversation

@nhorton

@nhorton nhorton commented Jan 16, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds explicit types: [checks_requested] to all merge_group triggers
  • Updates README.md to document this best practice

Problem

Jobs were not starting when PRs entered the merge queue. The workflows have merge_group triggers with branches: [main], but without the explicit types parameter, GitHub may not properly trigger the workflows.

Solution

GitHub documentation recommends explicitly specifying types: [checks_requested] for merge_group triggers:

"By default, a workflow only runs when a merge_group event's activity type is checks_requested. However, it is recommended to explicitly specify the activity type to be specific about which events trigger the workflow, because the default may change if more activity types are added in the future."

This change adds the recommended types: [checks_requested] to all three workflows that use merge_group:

  • validate.yml
  • claude-code-test.yml
  • cla.yml

Test plan

  • Merge this PR via the merge queue
  • Verify all jobs start and run correctly in the merge queue

🤖 Generated with Claude Code

GitHub documentation recommends explicitly specifying the activity type
for merge_group triggers. This ensures proper workflow triggering in the
merge queue and future-proofs against new activity types being added.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@nhorton
nhorton merged commit 0dbd512 into main Jan 16, 2026
6 checks passed
@nhorton
nhorton deleted the fix/merge-queue-types branch January 16, 2026 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant