T8764: skip auto-review of mergify[bot] backport PRs#2
Conversation
Adds `mergify[bot]` to `reviews.auto_review.ignore_usernames` in the central `vyos`-org CodeRabbit baseline. Mergify-opened backport PRs are mechanical cherry-picks of an already-reviewed source PR; re-reviewing them adds no signal and burns CodeRabbit's rate-limit budget. Manual `@coderabbitai review` continues to work for the rare case where a maintainer wants a fresh review on a backport PR (e.g. to confirm a conflict resolution was handled correctly after a non-clean cherry-pick). Behavior change observed today (2026-05-12): - vyos/vyos-documentation#2006 (sagitta) and #2007 (circinus) were auto-opened by Mergify as backports of #2005. Both got CodeRabbit auto-reviews despite being byte-equivalent to the already-reviewed source PR. This change suppresses that. Scope: central `vyos`-org baseline only. Mirror change on `VyOS-Networks/coderabbit:.coderabbit.yaml`. Related: T8782 (Mergify central-config rollout) — Mergify is the generator of these PRs; this is housekeeping on the CodeRabbit side. 🤖 Generated by [robots](https://vyos.io)
|
ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📜 Recent review details🧰 Additional context used🔍 Remote MCP Context7Perfect! I now have the relevant documentation. Let me provide the summary with appropriate citations. Additional Context for PR ReviewCodeRabbit Auto-Review Configuration -
|
| Layer / File(s) | Summary |
|---|---|
Early access and review configuration .coderabbit.yaml (lines 4–6, 29–41) |
early_access: true enabled with Org‑UI provenance (lines 4–6). Review behavior toggles added/adjusted: high_level_summary_in_walkthrough, review_details, fail_commit_status, in_progress_fortune, and auto_pause_after_reviewed_commits: 0 documented (lines 29–41). |
Auto-review bot exclusion .coderabbit.yaml (lines 52–59) |
reviews.auto_review.ignore_usernames introduced with mergify[bot] to skip automatic review for mechanically authored PRs; inline comment clarifies manual @coderabbitai review still works (lines 52–59). |
Automation toggles and tool configuration .coderabbit.yaml (lines 87–96, 108–148) |
finishing_touches.docstrings.enabled: false and finishing_touches.unit_tests.enabled: false set at org level (lines 87–96). Multiple fleet linters/checks disabled and Org‑UI provenance comments added; knowledge_base.mcp enabled and knowledge_base.linked_repositories added for Ansible cross-repo instructions (lines 108–148). |
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | Title accurately reflects the main change: adding mergify[bot] to ignore_usernames to skip auto-review of backport PRs. |
| Description check | ✅ Passed | Description comprehensively covers the change, rationale, trigger event, scope, and related references. |
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. |
| Linked Issues check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
✏️ Tip: You can configure your own custom pre-merge checks in the settings.
✨ Finishing Touches
🧪 Generate unit tests (beta)
- Create PR with unit tests
- Commit unit tests in branch
yuriy/t8764-ignore-mergify-bot
✨ Simplify code
- Create PR with simplified code
- Commit simplified code in branch
yuriy/t8764-ignore-mergify-bot
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.
Comment @coderabbitai help to get the list of available commands and usage tips.
|
@copilot review |
Reviewed the current change set in |
|
CodeRabbit chat interactions are restricted to organization members for this repository. Ask an organization member to interact with CodeRabbit, or set |
Moves every CodeRabbit setting currently configured in the `vyos`-org
Web UI dashboard ("Organization UI Settings", precedence #5) into the
Central YAML (precedence #3) so the file is the single source of truth
for review behavior in the `vyos` org. Once this lands, the Org-UI YAML
editor can be cleared and behavior will be unchanged.
Why this matters: precedence rules state that Central YAML overrides
Organization UI per-field. Today they happen to agree, but any future
edit to the Web UI silently drifts from the file. Consolidating into
YAML makes drift a code-review-visible event.
Lifted fields:
* Top-level:
- `early_access: false` -> `true` (matches Web UI explicit value)
* `reviews:`
- `high_level_summary_in_walkthrough: true`
- `review_details: true`
- `fail_commit_status: true`
- `estimate_code_review_effort: false`
- `in_progress_fortune: false`
* `reviews.auto_review:`
- `auto_pause_after_reviewed_commits: 0`
* `reviews.finishing_touches:`
- `unit_tests.enabled: true` -> `false` (matches Web UI intent; per-
repo overrides re-enable where appropriate — testing stacks differ
enough that fleet-wide unit-test generation is too noisy)
- `simplify.enabled: true`
* `reviews.tools:` disabled-linter list for stacks not in our fleet
(swiftlint, detekt, rubocop, regal, pmd, circleci, shopifyThemeCheck,
brakeman, blinter, smartyLint, emberTemplateLint)
* `chat:`
- `allow_non_org_members: false`
- `integrations.{jira,linear}.usage: disabled`
* `knowledge_base:`
- `{jira,linear}.usage: disabled`
- `mcp.usage: enabled`
- `linked_repositories: ansible/ansible` — cross-repo context for the
`vyos.vyos` Ansible Galaxy collection. vyos-org specific.
After this PR merges:
- Clear the Org-UI YAML editor in the CodeRabbit dashboard for the
`vyos` org (paste back the empty schema-comment line). The Central
YAML now expresses everything that was there.
- Sibling change for VyOS-Networks org on its own coderabbit central
repo (omits `linked_repositories` per org-specific scope; keeps
`early_access: false` since VyOS-Networks Org-UI did not set it).
🤖 Generated by [robots](https://vyos.io)
Sets `reviews.finishing_touches.docstrings.enabled: false` to match the already-disabled `unit_tests.enabled: false`. Same rationale: documentation conventions vary too much across the fleet for org-wide auto-generation to be useful — Python repos use Sphinx-style, Go repos use godoc-style, web repos use TSDoc-style. Repos that want CodeRabbit to fill in docstrings opt in via their own `.coderabbit.yaml`. 🤖 Generated by [robots](https://vyos.io)
Summary
Adds `mergify[bot]` to `reviews.auto_review.ignore_usernames` in the central CodeRabbit baseline for the `vyos` org. Mergify-opened backport PRs are mechanical cherry-picks of an already-reviewed source PR — re-reviewing them adds no signal and burns CodeRabbit's rate-limit budget. Manual `@coderabbitai review` continues to work for the rare case where a maintainer wants a fresh review on a backport PR.
Trigger
Observed today (2026-05-12): vyos/vyos-documentation#2006 (sagitta) and #2007 (circinus) were auto-opened by Mergify as backports of #2005. Both received CodeRabbit auto-reviews despite being byte-equivalent to the already-reviewed source PR. The new `ignore_usernames` entry suppresses that for every future Mergify-driven backport in the `vyos` org.
Scope
`vyos`-org central baseline only. Mirror change against `VyOS-Networks/coderabbit` in a sibling PR.
Per-repo overrides are still possible — if a downstream repo has unusual review needs for Mergify-authored PRs, it can re-enable via its own `.coderabbit.yaml` (override semantics per CodeRabbit's central-config inheritance).
Related
🤖 Generated by robots