ci(Mergify): configuration update

[unclesp1d3r]

This change has been made by @unclesp1d3r from the Mergify merge protections editor.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Summary by CodeRabbit

• Chores
  • Updated merge configuration to enforce stricter requirements for pull requests, ensuring branches remain synchronized with the main branch before merging.

Walkthrough

A merge protection rule is added to .mergify.yml that prevents merging pull requests when they are more than 10 commits behind the main branch, ensuring code stays current before integration.

Changes

Cohort / File(s)	Summary
Mergify Configuration .mergify.yml	Added merge_protections rule to prevent merging PRs that are outdated (commits-behind > 10) relative to main branch.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• ci(Mergify): add outdated PR protection #75: Adds the same "do not merge outdated PRs" merge_protections rule enforcing commits-behind threshold in Mergify configuration.

Suggested labels

size:S

Poem

🐰 Hops through the merge queue with glee,
Ten commits behind? "Not for me!"
Mergify keeps branches fresh and bright,
No stale PRs will slip through tonight! ✨

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch mergify/unclesp1d3r/I039705e36a3747c3ab01dc7ae8bdbda799e205fb

---

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

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 📃 Configuration Change Requirements

Wonderful, this rule succeeded.

Mergify configuration change

• check-success = Configuration changed

🟢 CI must pass

Wonderful, this rule succeeded.

All CI checks must pass or be legitimately skipped (path filtering). Matrix job names differ between running and skipped states, so the test-cross-platform rule uses an and/or pattern to handle both.

• any of:
  • check-skipped = quality
  • check-success = quality
• any of:
  • check-skipped = test
  • check-success = test
• any of:
  • check-skipped = test-cross-platform
  • all of:
    • check-success = test-cross-platform (macos-latest, macOS)
    • check-success = test-cross-platform (ubuntu-22.04, Linux)
    • check-success = test-cross-platform (ubuntu-latest, Linux)
    • check-success = test-cross-platform (windows-latest, Windows)
• any of:
  • check-skipped = coverage
  • check-success = coverage

🟢 Do not merge outdated PRs

Wonderful, this rule succeeded.

Make sure PRs are within 10 commits of the base branch before merging

• #commits-behind <= 10

[Copilot]

Pull request overview

Adds a Mergify merge_protections configuration to prevent merging PRs that are too far behind the main branch.

Changes:

• Introduces a “Do not merge outdated PRs” merge protection for PRs targeting main.
• Enforces a #commits-behind threshold via success_conditions.

[Copilot]

The protection description says PRs should be “almost up to date”, but the condition allows up to 10 commits behind. Either tighten the threshold (e.g., 0–1 commits behind) or adjust the wording so it matches the actual merge protection behavior.

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for 92e4d5c.

🟢 All jobs passed!

But CI Insights is watching 👀