chore: add mergify auto-merge for dependabot PRs - #149
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The Mergify rule omits gating on CI jobs that also run for Dependabot PRs (e.g., mutation tests/benchmarks), so it could merge even when those checks fail.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Adds a Mergify configuration to automatically squash-merge Dependabot PRs into main when the intended CI checks are green, avoiding skipped Dependabot-ineligible jobs as merge gates.
Changes:
- Introduces a
pull_request_rulesentry to auto-mergedependabot[bot]PRs targetingmain. - Defines required successful checks (unit tests per OS + API tests) before merging via squash.
File summaries
| File | Description |
|---|---|
| .github/mergify.yml | Adds Mergify rule to squash-merge Dependabot PRs when selected CI checks succeed. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Squash-merge Dependabot PRs into main once the CI checks that actually run for dependabot[bot] are green. Jobs guarded by `if: github.actor != 'dependabot[bot]'` are deliberately not used as gates: they are skipped on these PRs, and mergify counts a skipped check as skipped rather than successful, which would block the merge forever.
f5136da to
333283a
Compare
|
🚀 Benchmark ResultsDetails
|



Squash-merge Dependabot PRs into main once the CI checks that actually run for dependabot[bot] are green.
Jobs guarded by
if: github.actor != 'dependabot[bot]'are deliberately not used as gates: they are skipped on these PRs, and mergify counts a skipped check as skipped rather than successful, which would block the merge forever.