chore: make CodeRabbit advisory

[2gelbuy]

Makes CodeRabbit an assertive advisory reviewer instead of a hard workflow blocker: disables request-changes workflow, disables failed commit status, and disables auto-pause after 5 reviewed commits.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 7061fe8b-60d0-4a44-99f5-4a32c925bc20

📥 Commits

Reviewing files that changed from the base of the PR and between 2f64c7a and 8e47ca5.

📒 Files selected for processing (1)

• .coderabbit.yaml

📜 Recent 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). (1)

• GitHub Check: Agent

🔇 Additional comments (3)

.coderabbit.yaml (3)

6-6: Advisory workflow toggle is correctly configured.

request_changes_workflow: false matches the goal of avoiding hard blocking behavior.

---

21-21: Commit-status failure behavior is correctly relaxed.

fail_commit_status: false is consistent with an advisory setup and reduces hard-fail risk when CodeRabbit cannot review.

---

29-29: Auto-pause disabling is correctly set.

auto_pause_after_reviewed_commits: 0 is valid per schema and correctly disables the 5-commit auto-pause.

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated internal review automation configuration settings.

---

No changes visible to end-users in this release.

Walkthrough

This PR modifies .coderabbit.yaml to adjust review automation behavior: disabling request-changes workflow submission, disabling commit-status failure reporting, and resetting the auto-pause threshold from 5 reviewed commits to 0.

Changes

Review Automation Configuration

Layer / File(s)	Summary
Settings .coderabbit.yaml	reviews.request_changes_workflow is disabled; reviews.fail_commit_status is disabled; reviews.auto_pause_after_reviewed_commits is changed from 5 to 0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 7

✅ Passed checks (7 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title uses the conventional 'chore:' prefix and clearly describes the change to make CodeRabbit an advisory reviewer rather than a workflow blocker.
Description check	✅ Passed	The pull request description is directly related to the changeset, explaining the specific configuration changes made to CodeRabbit settings in the .coderabbit.yaml file.
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.
No Secrets	✅ Passed	No secrets detected. .coderabbit.yaml contains only configuration. Workflows use proper ${{ secrets.NAME }} GitHub Actions syntax. No hardcoded API keys, tokens, or credentials found.
Extension Permissions Safe	✅ Passed	PR does not modify extension permissions or host_permissions. Changes are limited to .coderabbit.yaml (review automation) and initial project files. No extension permission expansion occurred.

_{✏️ 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 coderabbit-advisory-20260510

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch coderabbit-advisory-20260510

• 🛠️ tighten validation: Commit on current branch
• 🛠️ tighten validation: Create PR

---

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