Skip to content

chore: add .coderabbit.yaml with request_changes_workflow#26

Merged
samuelho-dev merged 1 commit into
mainfrom
chore/coderabbit-config
May 8, 2026
Merged

chore: add .coderabbit.yaml with request_changes_workflow#26
samuelho-dev merged 1 commit into
mainfrom
chore/coderabbit-config

Conversation

@samuelho-dev

Copy link
Copy Markdown
Owner

Summary

  • Adds .coderabbit.yaml with reviews.request_changes_workflow: true so CodeRabbit posts a formal Approve / Request-Changes PR review (not just a walkthrough comment). This lets reviewDecision reflect CodeRabbit's verdict and lets branch-protection "Require approvals" use it as a real merge gate.
  • Pre-merge checks (title/description/docstrings) start in warning mode — non-blocking until we tune thresholds, then flip to error per-check.
  • auto_review.base_branches: [main] keeps reviews scoped to PRs targeting main.

Why

PR #24 surfaced that CodeRabbit was running but its result wasn't blocking merge — the pending Commit Status cleared during force-push and the merge happened before the re-review landed. With request_changes_workflow: true and "Require approvals" in branch protection, CodeRabbit's verdict becomes load-bearing.

Test plan

🤖 Generated with Claude Code

Makes CodeRabbit post a formal "Approve" / "Request Changes" PR review
(not just a walkthrough comment), so reviewers see the verdict in
`reviewDecision` and branch protection's "Require approvals" can rely
on it as a merge gate.

Pre-merge checks (title/description/docstrings) start in `warning` mode
to avoid blocking shipping while we tune. Flip to `error` per-check once
the team is comfortable.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented May 8, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@samuelho-dev has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 46 minutes and 16 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 73a8682d-52c2-4aab-8a66-4f6c014582a5

📥 Commits

Reviewing files that changed from the base of the PR and between bf7d87c and 96a9c1e.

📒 Files selected for processing (1)
  • .coderabbit.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/coderabbit-config

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

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

@samuelho-dev samuelho-dev merged commit bd55caa into main May 8, 2026
6 checks passed
@samuelho-dev samuelho-dev deleted the chore/coderabbit-config branch May 8, 2026 04:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant