Conversation
There was a problem hiding this comment.
🟢 Approval recommended
The Mergify rule is narrowly scoped to Dependabot PRs and targets the existing CI “Unit tests” matrix check names that run on those PRs.
Pull request overview
Adds a Mergify configuration to automatically squash-merge Dependabot PRs into main once the unit test matrix checks complete successfully, aligning the merge gate with the checks that actually run for dependabot[bot].
Changes:
- Add a Mergify pull request rule scoped to
base = mainandauthor = dependabot[bot]. - Gate auto-merge on the three OS-specific “Unit tests” check runs and use
squashas the merge method.
File summaries
| File | Description |
|---|---|
| .github/mergify.yml | Introduces a Mergify rule to auto-squash-merge Dependabot PRs after the unit test checks succeed on ubuntu/windows/macos. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- 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.
cf8b8df to
b727f57
Compare
|
There was a problem hiding this comment.
🟡 Changes recommended
The Mergify check-success contexts likely don’t match the actual GitHub Actions check names, which would prevent auto-merge from ever triggering.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 1
- Review effort level: Lite
| - check-success = Unit tests (ubuntu-latest) | ||
| - check-success = Unit tests (windows-latest) | ||
| - check-success = Unit tests (macos-latest) |
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.