chore(coderabbit): enable proplus review config#248
Conversation
|
@coderabbitai autofix |
|
Warning
|
| Layer / File(s) | Summary |
|---|---|
Core review and path rules .coderabbit.yaml |
Aktiviert request_changes_workflow, erweitert Review-Artefakte, erweitert reviews.labeling_instructions mit auto_apply_labels, und führt ein Ausschluss-basiertes path_filters Baseline ein. |
Path-specific instructions & plugin invariants .coderabbit.yaml |
Schreibt path_instructions für TS/JS/JSON, Tests, Python, GitHub Workflows, Markdown/Docs und generierte Dateien um; fügt strikte strukturelle Invarianten für plugins/ancplua/** (Ausführungsmodell, Playwright-only Oracle via Screenshots, atomare Locks, Autoscaling/Spawn-Regeln) hinzu. |
Auto-review, finishing passes, pre-merge checks & tools .coderabbit.yaml |
Aktiviert Slop-Detection und auto_review (Draft-Verhalten, Title-Ignore), erweitert finishing_touches (Docstrings, Unit-Tests, benannte Pässe), verschärft pre_merge_checks (Secrets/PII, Generated regen, Async/Cancellation, CI/Changelog/Dependency/Path/C#-Ban, SKILL frontmatter, marketplace sync) und erweitert das tools-Matrix (z.B. opengrep, semgrep, trivy, pylint, oxc, actionlint, osvScanner, presidio, htmlhint). |
Knowledge base & code-generation .coderabbit.yaml |
Setzt chat.allow_non_org_members: false, erweitert knowledge_base.code_guidelines.filePatterns, ändert learnings/issues/pull_requests Scope zu global, aktiviert MCP und linked_repositories, und fügt code_generation Regeln sowie issue_enrichment/auto-planning mit Label-Autoapply hinzu. |
Estimated code review effort
🎯 4 (Complex) | ⏱️ ~45 minutes
Possibly related PRs
- ANcpLua/ancplua-claude-plugins#224: Überlappt stark bei
.coderabbit.yaml-Änderungen zu Review-Automation, Labeling und Path/Tools-Konfiguration.
Suggested labels
area:feature-dev
Suggested reviewers
- github-actions
"Ich bin ein Hoppel-Reviewer, flink und keck,
Schreib' Docstrings, Tests – ich geb' nicht weg.
Konfig erneuert, Regeln fein gezogen,
Plugins gehopst, die Prüfungen sind begonnen.
🐇✨"
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
| Check name | Status | Explanation |
|---|---|---|
| Description Check | ✅ Passed | Check skipped - CodeRabbit’s high-level summary is enabled. |
| Title check | ✅ Passed | Der Titel 'chore(coderabbit): enable proplus review config' beschreibt präzise die Hauptänderung: Aktivierung der CodeRabbit Pro+-Konfiguration für die Repository. Er ist spezifisch, prägnant und vermittelt deutlich den Kernzweck der Änderung. |
| 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
dev/coderabbit-proplus-20260516155428
Comment @coderabbitai help to get the list of available commands and usage tips.
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found. |
|
Claude encountered an error after 2s —— View job I'll analyze this and get back to you. |
Up to standards ✅🟢 Issues
|
There was a problem hiding this comment.
Pull Request Overview
The upgrade to CodeRabbit Pro+ configuration introduces a robust security and validation suite; however, several internal contradictions must be resolved before merging.
The most significant conflict is the 'No C# or .NET' policy, which is undermined by specific AI instructions to generate C# code and documentation. Additionally, some file patterns are excluded globally via path_filters while simultaneously having detailed path_instructions defined, making those instructions unreachable. These issues will lead to inconsistent AI behavior and potential workflow failures. While Codacy grades the change as up to standards, the functional gaps in the configuration logic are the main barriers to a successful deployment.
Test suggestions
- Verify that .coderabbit.yaml is valid against the CodeRabbit v2 JSON schema.
- Ensure the request-changes workflow correctly blocks PRs when error-mode checks (like 'No Secrets') fail.
- Confirm that path-specific instructions for 'plugins/ancplua/' correctly trigger Playwright-only validation logic.
- Validate that the 'No C# or .NET code' pre-merge check accurately identifies and blocks .cs or .csproj files.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Ensure the request-changes workflow correctly blocks PRs when error-mode checks (like 'No Secrets') fail.
2. Confirm that path-specific instructions for 'plugins/ancplua/' correctly trigger Playwright-only validation logic.
3. Validate that the 'No C# or .NET code' pre-merge check accurately identifies and blocks .cs or .csproj files.
Low confidence findings
- The 'path_filters' section has transitioned to a large number of negative exclusion patterns. This approach carries the risk of inadvertently including files in the root or unexpected directories that were previously filtered out by the more explicit inclusion-based configuration. Suggest a sanity check to ensure no sensitive or irrelevant directories are being indexed.
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
| - "!**/*.g.cs" | ||
| - "!**/*.g.ts" | ||
| - "!**/*.g.sql" | ||
| - "!**/*.g.tsp" | ||
| - "!**/*.Designer.cs" | ||
| - "!**/Generated/**" |
There was a problem hiding this comment.
🟡 MEDIUM RISK
The instructions for generated files (e.g., **/*.g.cs, **/*.g.ts) defined in path_instructions (lines 175-179) are currently unreachable because these same patterns are explicitly excluded in the path_filters section (lines 120-123). If you want the 'Generated-output discipline' rules to be applied, remove these patterns from the exclusion list; otherwise, remove the redundant instructions.
| - path: "**/*.cs" | ||
| instructions: Generate XML docs for public/protected APIs and package surfaces. | ||
| Document intent, contracts, cancellation, exceptions, and compatibility. Do | ||
| not add obvious comments to private implementation details. | ||
| - path: "**/*.{ts,tsx}" | ||
| instructions: Generate concise TSDoc only for exported APIs, hooks, reusable | ||
| components, schemas, and non-obvious utility behavior. Avoid restating prop | ||
| names. | ||
| unit_tests: | ||
| path_instructions: | ||
| - path: "**/*.cs" | ||
| instructions: Use the repo test stack (xUnit v3/Microsoft Testing Platform where | ||
| present). Prefer focused unit tests plus integration tests for persistence, | ||
| queues, external clients, and generated contracts. Avoid sleeps; use fakes/signals. | ||
| - path: "**/*.{ts,tsx}" |
There was a problem hiding this comment.
🟡 MEDIUM RISK
This configuration contains a logical contradiction that will lead to invalid AI suggestions. A pre-merge error check is defined at line 465 to strictly prohibit C# or .NET code, yet lines 683-697 provide specific instructions for generating C# code, docstrings, and unit tests. To maintain a consistent policy, remove these C# specific instructions and guidelines (including .NET patterns in code_guidelines at lines 609-614).
|
@coderabbitai autofix |
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found. |
|
Claude encountered an error after 2s —— View job I'll analyze this and get back to you. |
There was a problem hiding this comment.
Pull request overview
This PR replaces the repository’s CodeRabbit v2 configuration with a Pro+ / enterprise-grade setup intended to increase review depth (request-changes workflow, expanded review detail, pre-merge checks, more analyzers, web/MCP knowledge, issue enrichment, and finishing touches).
Changes:
- Enables stricter review gating (request-changes workflow + failing commit status) and expands review features (summaries, diagrams, linked issues/PRs).
- Adds/expands pre-merge checks and finishing-touch “recipes” (security/test/docs/perf passes).
- Enables a broader set of static-analysis/security tools and knowledge sources (web search + MCP + linked repos).
| - reviewers: | ||
| - handle: ANcpLua | ||
| type: user | ||
| instructions: Suggest for PRs touching architecture, public APIs, security-sensitive | ||
| code, release automation, generated artifacts, or cross-repository contracts. |
| path_filters: | ||
| - plugins/** | ||
| - docs/** | ||
| - tooling/** | ||
| - .github/** | ||
| - .claude/** | ||
| - .claude-plugin/** | ||
| - CLAUDE.md | ||
| - AGENTS.md | ||
| - CHANGELOG.md | ||
| - '*.json' | ||
| - '*.sh' | ||
| - '*.md' | ||
| - '*.yaml' | ||
| - '*.yml' | ||
| - '!**/node_modules/**' | ||
| - '!**/.git/**' | ||
|
|
||
| # ── Path instructions ───────────────────────────────────────────────────── | ||
| - "!**/bin/**" | ||
| - "!**/obj/**" | ||
| - "!**/dist/**" | ||
| - "!**/node_modules/**" |
| unhappy paths, loading states, and accessibility-critical behavior when UI logic | ||
| changes. | ||
| - path: "**/*.py" | ||
| instructions: Python review. Flag broad except blocks, implicit network/file side | ||
| effects, untyped public functions, path traversal risks, nondeterministic temp-file | ||
| handling, dependency pin drift, missing timeouts, and tests that require live | ||
| services without explicit gating. | ||
| - path: ".github/workflows/**" | ||
| instructions: GitHub Actions review. Pin third-party actions to immutable SHAs | ||
| unless the repo explicitly documents tag-pinning; keep permissions minimal per | ||
| job; use concurrency for push/PR workflows; avoid secrets in command lines/logs; | ||
| keep required and non-blocking jobs clear; preserve tokenless OIDC upload patterns | ||
| where used; and flag any admin-bypass, force-push, destructive cleanup, or auto-merge | ||
| behavior that can mask a failed required check. | ||
| - path: "**/*.{md,mdx}" | ||
| instructions: 'Documentation review. Treat docs as executable team memory: flag | ||
| instructions that disagree with actual scripts, package versions, branch protection, | ||
| generated-file workflows, or repo layout. Keep AGENTS.md/CLAUDE.md rules coherent | ||
| with automation. Do not request cosmetic prose changes unless ambiguity would | ||
| mislead an agent or maintainer.' | ||
| - path: "**/*.{g.cs,g.ts,g.sql,g.tsp,Designer.cs,generated.*,snap}" | ||
| instructions: Generated-output discipline. Do not suggest hand-editing generated | ||
| files. If generated output is wrong or missing, identify the generator/source | ||
| input and require regeneration in the same PR. If source model changes without | ||
| matching generated artifacts, flag it. |
| deserialization, authz/authn drift, overbroad logging, unsafe dependency changes, | ||
| and CI token permission expansion. Apply minimal fixes directly when safe; | ||
| otherwise leave precise comments. | ||
| - enabled: true | ||
| name: test gap closure | ||
| instructions: Generate focused tests for changed behavior and edge cases. Prefer | ||
| existing test frameworks and fixtures. Do not create broad snapshot churn | ||
| or tests that merely assert implementation details. Include regression tests | ||
| for bugs and riskier boundary changes. | ||
| - enabled: true | ||
| name: docs and changelog alignment | ||
| instructions: Update docs, README, AGENTS/CLAUDE guidance, generated reference | ||
| docs, and changelog entries only where the PR changes user-visible behavior, | ||
| public contracts, workflows, or agent instructions. Keep entries concise and | ||
| consistent with repo rules. | ||
| - enabled: true | ||
| name: performance and allocation pass | ||
| instructions: Review changed hot paths for avoidable allocations, repeated parsing, | ||
| unbounded concurrency, N+1 calls, missing streaming/backpressure, and inefficient | ||
| data structures. Apply low-risk improvements with tests or benchmarks where | ||
| the repo already has them. | ||
| pre_merge_checks: | ||
| override_requested_reviewers_only: true | ||
| docstrings: | ||
| mode: 'off' | ||
| mode: warning | ||
| threshold: 75 | ||
| title: | ||
| mode: error | ||
| requirements: >- | ||
| Conventional commits: feat|fix|refactor|chore|docs|test|ci|perf. | ||
| Include scope matching plugin name or area: (exodia), (metacognitive-guard), | ||
| (hookify), (feature-dev), (dotnet-lint), (routing), (council), | ||
| (design-studio), (elegance), (code-simplifier), (qyl), (otelhook), | ||
| (ancplua), (rider-respect), (release-pilot), (infra), (docs), (ci). | ||
| Under 72 characters. No trailing period. | ||
| Examples: feat(exodia): add baryon-mode command, fix(hookify): escape regex in rule matching | ||
| requirements: Conventional commits with an area scope; under 72 characters; | ||
| no trailing punctuation; accurately names the highest-impact change. | ||
| description: |
| be updated in the same PR. Fail if generated files appear hand-edited without | ||
| the source generator/input change, or if generated output is missing after | ||
| source-model changes.' | ||
| - mode: error | ||
| name: Async And Cancellation Safe | ||
| instructions: 'Pass/fail criteria: fail C#/TS/Python changes that introduce | ||
| sync-over-async, unobserved fire-and-forget work, missing CancellationToken/AbortSignal | ||
| propagation on public/internal async boundaries, sleeps for synchronization, | ||
| or resource disposal paths that can drop in-flight work.' | ||
| - mode: error | ||
| name: Public Contract Documented | ||
| instructions: 'Pass/fail criteria: fail if public APIs, endpoint schemas, CLI | ||
| flags, config keys, package surfaces, storage formats, event schemas, MCP | ||
| tool schemas, or generated contracts change without matching docs/tests and | ||
| explicit compatibility notes in the PR description or changelog where the | ||
| repo uses one.' | ||
| - mode: error | ||
| name: CI Release Safety | ||
| instructions: 'Pass/fail criteria: fail workflow/build/release changes that | ||
| reduce required validation, introduce admin bypasses, broaden token permissions | ||
| without justification, leak secrets, remove concurrency where needed, make | ||
| publish steps run on the wrong trigger, or allow failed required checks to | ||
| be ignored.' | ||
| - mode: warning | ||
| name: Tests Match Risk | ||
| instructions: 'Pass/fail criteria: warn when production behavior changes without | ||
| focused tests or when tests only assert implementation details. Require integration/e2e | ||
| coverage for persistence, queues, external-service boundaries, generated contracts, | ||
| migrations, or user-visible workflows touched by the PR.' | ||
| - mode: warning | ||
| name: No Copy Paste Tables | ||
| instructions: 'Pass/fail criteria: warn when a PR introduces hardcoded repetitive | ||
| case lists, hand-maintained mapping tables, duplicate switch branches, or | ||
| parallel arrays where a data-driven or generated structure would be more maintainable. |
| - label: security | ||
| instructions: Apply when the issue involves secrets, auth, privacy, dependency | ||
| risk, or exploitability. | ||
| - label: dependencies | ||
| instructions: Apply when the issue is about package, SDK, runtime, or lockfile |
| - path: "**/*.cs" | ||
| instructions: Use the repo test stack (xUnit v3/Microsoft Testing Platform where | ||
| present). Prefer focused unit tests plus integration tests for persistence, | ||
| queues, external clients, and generated contracts. Avoid sleeps; use fakes/signals. | ||
| - path: "**/*.{ts,tsx}" | ||
| instructions: Use the repo frontend test stack. Assert user-visible behavior | ||
| and accessible roles/states. Avoid waitForTimeout and brittle snapshots. | ||
| - path: "**/*.py" | ||
| instructions: Use pytest-style focused tests where a Python test stack exists. | ||
| Mock network and filesystem boundaries unless explicitly live-gated. | ||
| issue_enrichment: | ||
| auto_enrich: | ||
| enabled: true | ||
| planning: | ||
| enabled: true | ||
| auto_planning: | ||
| enabled: false | ||
| enabled: true | ||
| labels: | ||
| - plan:auto | ||
| - enhancement |
| unit_tests: | ||
| enabled: false | ||
|
|
||
| # ── Pre-merge checks ───────────────────────────────────────────────────── | ||
| enabled: true | ||
| simplify: | ||
| enabled: true | ||
| custom: |
| - label: area:api | ||
| instructions: Apply when REST, RPC, MCP, public endpoints, contracts, or request/response | ||
| models change. | ||
| - label: area:ui | ||
| instructions: Apply when frontend UI, styling, accessibility, or client-side state | ||
| changes. | ||
| - label: area:build | ||
| instructions: Apply when build scripts, NUKE/MSBuild, package managers, Docker, | ||
| CI, or release automation change. | ||
| - label: area:test | ||
| instructions: Apply when tests, fixtures, test infrastructure, coverage, or snapshots | ||
| change. | ||
| - label: area:docs | ||
| instructions: Apply when docs, AGENTS.md, CLAUDE.md, README, changelogs, specs, | ||
| or generated reference docs change. | ||
| - label: area:security | ||
| instructions: Apply when authentication, authorization, secrets, token handling, | ||
| logging of sensitive data, or dependency security changes. | ||
| - label: area:data | ||
| instructions: Apply when database schema, persistence, migrations, queues, storage, | ||
| serialization, generated data, or data contracts change. | ||
| - label: area:agents |
| version, description accuracy matching actual plugin capabilities, and that | ||
| the name matches the directory name. Flag missing fields as blocking. Flag version | ||
| that wasn''t bumped when plugin code changed.' | ||
| - path: plugins/**/SKILL.md |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.coderabbit.yaml:
- Around line 703-778: The duplicate label definitions under
issue_enrichment.labeling.labeling_instructions exactly mirror
reviews.labeling_instructions and risk drift; remove the duplicated block and
replace it with a single source of truth: either (preferred) refactor to use a
YAML anchor/alias (define the labels once, reference them in both
issue_enrichment.labeling and reviews) using the existing label list as the
canonical definition, or if anchors are unsupported, keep only one label block
and add a clear comment in both places pointing to the canonical section (or
switch to generating the config from a single template); update references to
the canonical symbol (issue_enrichment.labeling.labeling_instructions or
reviews.labeling_instructions) accordingly so both consumers use the same
definition.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 30384996-fae5-490b-8253-2a19e91663b7
📒 Files selected for processing (1)
.coderabbit.yaml
📜 Review details
⏰ Context from checks skipped due to timeout of 900000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: copilot-pull-request-reviewer
- GitHub Check: Codacy Static Code Analysis
🧰 Additional context used
🔀 Multi-repo context ANcpLua/ANcpLua.Agents, ANcpLua/ANcpLua.Analyzers, ANcpLua/ANcpLua.NET.Sdk, O-ANcppLua/ANcpLua.OtelConventions.Api, ANcpLua/ANcpLua.Roslyn.Utilities, ANcpLua/Arqio, ANcpLua/BSc_2025_Alexander_Nachtmann, ANcpLua/ErrorOrX, O-ANcppLua/Nuke.OpenTelemetry.Conventions
[::ANcpLua/ANcpLua.Agents::]
- .coderabbit.yaml present at repo root; references coderabbit schema and path_instructions. [::ANcpLua/ANcpLua.Agents::]
- .github/workflows/coderabbit-autofix.yml and .github/workflows/claude-code-review.yml reference coderabbit/autofix bot behavior and review steps (lines show actor checks, autofix comment body, group naming). [::ANcpLua/ANcpLua.Agents::]
[::ANcpLua/ANcpLua.Analyzers::]
- .coderabbit.yaml present at repo root (schema-validated header). [::ANcpLua/ANcpLua.Analyzers::]
- .github/workflows/coderabbit-autofix.yml and .github/workflows/claude-code-review.yml reference coderabbit actor and instruct reading .coderabbit.yaml for repo invariants. [::ANcpLua/ANcpLua.Analyzers::]
[::ANcpLua/ANcpLua.NET.Sdk::]
- .coderabbit.yaml at repo root; workflows (.github/workflows/claude-code-review.yml, coderabbit-autofix.yml, auto-merge.yml) check for coderabbit bot actor and instruct reading .coderabbit.yaml for repo invariants. [::ANcpLua/ANcpLua.NET.Sdk::]
[::O-ANcppLua/ANcpLua.OtelConventions.Api::]
- .coderabbit.yaml exists and includes notes about per-repo overrides and pre_merge_checks. [::O-ANcppLua/ANcpLua.OtelConventions.Api::]
[::ANcpLua/ANcpLua.Roslyn.Utilities::]
- .coderabbit.yaml present (contains placeholders like high_level_summary_placeholder, auto_title_placeholder, description_keyword). Workflow files also reference coderabbit/autofix and claude review. [::ANcpLua/ANcpLua.Roslyn.Utilities::]
[::ANcpLua/Arqio::]
- .coderabbit.yaml present with per-repo override comments and pre_merge_checks notes. [::ANcpLua/Arqio::]
[::ANcpLua/BSc_2025_Alexander_Nachtmann::]
- .coderabbit.yaml present with per-repo override comments and pre_merge_checks notes. [::ANcpLua/BSc_2025_Alexander_Nachtmann::]
[::ANcpLua/ErrorOrX::]
- .coderabbit.yaml present; .github/workflows/auto-merge.yml includes coderabbit-auto-merge job and checks for coderabbit bot review user. [::ANcpLua/ErrorOrX::]
[::O-ANcppLua/Nuke.OpenTelemetry.Conventions::]
- .coderabbit.yaml present with per-repo override comments and pre_merge_checks notes. [::O-ANcppLua/Nuke.OpenTelemetry.Conventions::]
Implication summary: Multiple repositories already contain per-repo .coderabbit.yaml and GitHub workflows that integrate with CodeRabbit (autofix, auto-merge, claude-code-review). The PR’s changes to the root .coderabbit.yaml (enabling Pro+ features, stricter pre-merge checks, and expanded path_instructions) likely overlap with these per-repo configs and the existing workflows — coordinate review/autofix/auto-merge behavior and ensure per-repo overrides remain compatible with the new Pro+ defaults.
🔇 Additional comments (10)
.coderabbit.yaml (10)
1-20: LGTM!
21-107: LGTM!
108-143: LGTM!
144-316: LGTM!
317-333: LGTM!
334-372: LGTM!
373-480: LGTM!
481-585: LGTM!
586-594: LGTM!
595-678: LGTM!
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d34ac8baae
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - "!**/*.Designer.cs" | ||
| - "!**/Generated/**" | ||
| - "!**/generated/**" | ||
| - "!**/bin/**" |
There was a problem hiding this comment.
Stop excluding plugin bin scripts from review scope
reviews.path_filters is evaluated before path-specific guidance, so !**/bin/** removes every plugins/**/bin/*.sh file from CodeRabbit’s review surfaces. That makes the dedicated shell-script checks later in this config unreachable for bin scripts, so risky release/helper shell changes can bypass the quoting/error-handling checks this file explicitly intends to enforce.
Useful? React with 👍 / 👎.
| - "!**/*.g.cs" | ||
| - "!**/*.g.ts" | ||
| - "!**/*.g.sql" | ||
| - "!**/*.g.tsp" |
There was a problem hiding this comment.
Include .g. outputs when enforcing generated-file drift*
The config excludes *.g.cs, *.g.ts, *.g.sql, and *.g.tsp in path_filters, but also adds generated-output review instructions and a pre-merge policy that depends on reviewing generated artifacts for drift. With these exclusions, the most common generated outputs are skipped entirely, so regeneration regressions in .g.* files can pass without the intended review enforcement.
Useful? React with 👍 / 👎.
|
@coderabbitai autofix |
|
Claude encountered an error after 2s —— View job I'll analyze this and get back to you. |
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found. |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
@coderabbitai autofix |
|
Claude encountered an error after 2s —— View job I'll analyze this and get back to you. |
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found. |
|
@coderabbitai autofix |
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found. |
|
Claude encountered an error after 2s —— View job I'll analyze this and get back to you. |
Up to standards ✅🟢 Issues
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a72abd42ae
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| mcp: | ||
| usage: auto | ||
|
|
||
| # ── Issue enrichment ────────────────────────────────────────────────────── | ||
| enabled: true |
There was a problem hiding this comment.
Use
usage for MCP knowledge-base setting
Replace the boolean knowledge_base.mcp.enabled with the supported usage field (auto|enabled|disabled). CodeRabbit’s MCP configuration expects usage, so this setting will not reliably force MCP on and can silently fall back to defaults (for public repos, that means MCP is off), which defeats the commit’s stated goal of enabling MCP-backed review context.
Useful? React with 👍 / 👎.
|
@coderabbitai autofix |
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found. |
|
pr-heal: providers tried — CodeRabbit autofix=true, Claude=failure. None resolved the block (state was BLOCKED). Next sweep in 15 min; if this is recurring, the Codex/Copilot fallback tiers are tracked in pr-heal.yml. |
|
@coderabbitai autofix |
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found. |
|
pr-heal: providers tried — CodeRabbit autofix=true, Claude=failure. None resolved the block (state was BLOCKED). Next sweep in 15 min; if this is recurring, the Codex/Copilot fallback tiers are tracked in pr-heal.yml. |
|
pr-heal: providers tried — CodeRabbit autofix=skipped, Claude=failure. None resolved the block (state was BEHIND). Next sweep in 15 min; if this is recurring, the Codex/Copilot fallback tiers are tracked in pr-heal.yml. |
2 similar comments
|
pr-heal: providers tried — CodeRabbit autofix=skipped, Claude=failure. None resolved the block (state was BEHIND). Next sweep in 15 min; if this is recurring, the Codex/Copilot fallback tiers are tracked in pr-heal.yml. |
|
pr-heal: providers tried — CodeRabbit autofix=skipped, Claude=failure. None resolved the block (state was BEHIND). Next sweep in 15 min; if this is recurring, the Codex/Copilot fallback tiers are tracked in pr-heal.yml. |
Dismissed by github-settings-automation: CodeRabbit is advisory-only under the new posture (request_changes_workflow: false); see https://github.com/ANcpLua/github-settings-automation#auto-merge-posture
|
pr-heal: providers tried — CodeRabbit autofix=skipped, Claude=failure. None resolved the block (state was BEHIND). Next sweep in 15 min; if this is recurring, the Codex/Copilot fallback tiers are tracked in pr-heal.yml. |
1 similar comment
|
pr-heal: providers tried — CodeRabbit autofix=skipped, Claude=failure. None resolved the block (state was BEHIND). Next sweep in 15 min; if this is recurring, the Codex/Copilot fallback tiers are tracked in pr-heal.yml. |
|
@coderabbitai autofix |
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found. |
pr-heal: auto-fix tiers exhausted
Block state: If tier 3 produced a useful diagnosis it is in the comment above this one. |
|
@coderabbitai autofix |
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found. |
pr-heal: auto-fix tiers exhausted
Block state: If tier 3 produced a useful diagnosis it is in the comment above this one. |
|
Closing — superseded / stale; reopen if you want to revisit. |
|
@coderabbitai autofix |
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found. |
What changed
Why
We have the paid CodeRabbit capacity; this makes CodeRabbit spend it on review depth instead of staying on the old advisory baseline.
Validation
https://coderabbit.ai/integrations/schema.v2.json, docs last updated 2026-05-10)..coderabbit.yamllocally against the live schema before pushing this branch.Summary by CodeRabbit
Versionsnotizen