chore: fail CodeRabbit status check when review is skipped

[euxaristia]

Summary

CodeRabbit reports a green SUCCESS commit status even when rate limited and the PR was never actually reviewed (seen on #43: "Review rate limited"). This is misleading when used as a required status check.

Adding .coderabbit.yaml with fail_commit_status: true so skipped reviews fail the check instead of silently passing.

Changes

• .coderabbit.yaml: new file with fail_commit_status: true, request_changes_workflow: false

Test plan

• Open a PR when CodeRabbit is rate limited and verify the commit status reports failure instead of success
• Alternatively, comment @coderabbitai configuration on this PR to confirm the config is picked up

Fixes #52

[coderabbitai]

Warning

Ignoring CodeRabbit configuration file changes. For security, only the configuration from the base branch is applied for open source repositories.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 65461486-8bc8-4696-a3c1-cf2e1974ab6f

📥 Commits

Reviewing files that changed from the base of the PR and between 4208cd2 and 656f6f2.

📒 Files selected for processing (1)

• .coderabbit.yaml

---

📝 Walkthrough

Walkthrough

Adds a .coderabbit.yaml configuration that sets the review language and controls CodeRabbit status reporting, failure handling, and automatic change-request behaviour.

Changes

CodeRabbit configuration

Layer / File(s)	Summary
Review status settings .coderabbit.yaml	Configures English (United States) reviews, commit and review status reporting, failed commit statuses when reviews cannot be completed, and disables the request-changes workflow.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Poem

A rabbit tucked settings neat,
So review checks are clear and fleet.
If rate limits block the way,
The status won’t pretend “hooray.”
Configured with care,
It hops through review affairs.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the main change: making CodeRabbit fail the status check when review is skipped.
Description check	✅ Passed	The description accurately describes the config change and its purpose, and it aligns with the PR summary.
Linked Issues check	✅ Passed	The PR implements #52 by adding .coderabbit.yaml with fail_commit_status enabled to avoid false green checks.
Out of Scope Changes check	✅ Passed	The change set appears limited to the CodeRabbit configuration required by the issue, with no unrelated additions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/coderabbit-fail-commit-status

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 Checkov (3.3.8)

.coderabbit.yaml

Traceback (most recent call last):
File "/usr/local/bin/checkov", line 2, in
from checkov.main import Checkov
ModuleNotFoundError: No module named 'checkov'

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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