ci: Configure Mergify for sequential PR processing

[ashleyshaw]

Summary

Configure Mergify for sequential PR processing to resolve branch-protection conflict.

Changes

• Add batch_size: 1 to queue rules (sequential processing)
• Add merge_queue: { max_parallel_checks: 1 } (in-place checks)
• Add merge_conditions to Dependabot queue (safety checkpoint)

Why

Resolves Mergify/branch-protection incompatibility. Sequential checks work with GitHub's "Require branches to be up to date before merging" rule via auto-rebase.

Linked Issues

Resolves: Mergify queue blocked by branch-protection conflict (Option B implementation)

Checklist (Global DoD / PR)

• All AC met
• No tests needed (config only)
• CI green
• Ready for merge

🤖 Generated with Claude Code

[ashleyshaw]

@Mergifyio queue

Merging Mergify sequential config to unblock PR #1656 and PR #1658.

🤖 Queued by Claude Code

[coderabbitai]

Warning

Review limit reached

@ashleyshaw, you've reached your PR review limit, so we couldn't start this review.

Next review available in:57 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 482f3fa3-df50-474f-9025-3d3ec83bce22

📥 Commits

Reviewing files that changed from the base of the PR and between 40d2f10 and 6b8f74b.

📒 Files selected for processing (1)

• .github/mergify.yml

---

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

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

[github-actions]

⚠️ A merged PR reached develop without passing the template content guardrail.

Missing required section(s): Linked issues, Changelog, Global DoD checklist

This is a post-merge backstop for admin bypasses. Please review branch protection for develop.

[github-actions]

⏱️ Aging and SLA annotation

• Age: 0 day(s)
• SLA state: Within SLA
• Thresholds: warn at 7 days, breach at 14 days
• Last updated: 2026-08-09T10:27:41.152Z

Maintained by project-meta-sync workflow.

[mergify]

Merge Queue Status

• 🟠 Waiting for queue conditions
• ⏳ Enter queue
• ⏳ Run checks
• ⏳ Merge

Waiting for

• -closed [📌 queue requirement]
• any of: [📌 queue requirement]
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections
• any of: [🔀 queue conditions]
  • check-neutral = validate-pr-template
  • check-skipped = validate-pr-template
  • check-success = validate-pr-template

All conditions

• -closed [📌 queue requirement]
• any of [📌 queue requirement]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections
• any of [🔀 queue conditions]:
  • all of [📌 queue conditions of queue rule dependabot-develop]:
    • any of [🛡 GitHub branch protection]:
      • check-neutral = validate-pr-template
      • check-skipped = validate-pr-template
      • check-success = validate-pr-template
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• any of [📌 queue -> configuration change requirements]:
  • -mergify-configuration-changed
  • check-success = Configuration changed

[mergify]

Merge Protections

🔴 1 of 2 protections blocking · waiting on 🤖 CI

	Protection	Waiting on
🔴	📃 Configuration Change Requirements	🤖 CI
🟢	🚦 Auto-queue	—

🔴 📃 Configuration Change Requirements

Waiting for

• check-success = Configuration changed

This rule is failing.

Mergify configuration change

• check-success = Configuration changed

---

Show 1 satisfied protection

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

[github-actions]

🔍 Reviewer Summary for PR #1660

CI Status: ✅ success
Files changed: 1
Risk Distribution: 0 critical, 1 high, 0 medium, 0 low

Recommendations

• Ready to proceed pending human review

---