Skip to content

Disable coderabbit on bump prs#520

Open
MartelliEnrico wants to merge 2 commits into
mainfrom
disable-coderabbit-on-bump-prs
Open

Disable coderabbit on bump prs#520
MartelliEnrico wants to merge 2 commits into
mainfrom
disable-coderabbit-on-bump-prs

Conversation

@MartelliEnrico

@MartelliEnrico MartelliEnrico commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Just treat them as any other prs from dependabot or similar

Summary by CodeRabbit

  • Chores
    • Enabled automated code reviews with configuration to exclude dependency bump PRs from auto-review
    • Updated dependency update pull request titles to include a "[bump]" prefix for improved identification

Just treat them as any other prs from dependabot or similar
@coderabbitai

coderabbitai Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@MartelliEnrico, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 55 minutes and 16 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5cc41c6c-7d52-44ee-8b71-6b9c06e0e0aa

📥 Commits

Reviewing files that changed from the base of the PR and between 4c31b3e and 1768aea.

📒 Files selected for processing (1)
  • .github/workflows/bump.yaml
📝 Walkthrough

Walkthrough

A .coderabbit.yaml file is introduced, configuring auto_review to skip PRs whose title contains [bump]. The bump workflow's title_template is updated to prepend [bump] to generated PR titles, matching that ignore rule.

Changes

Bump PR auto-review suppression

Layer / File(s) Summary
[bump] title prefix and CodeRabbit ignore rule
.github/workflows/bump.yaml, .coderabbit.yaml
title_template in the bump workflow is updated to prefix titles with [bump], and the new .coderabbit.yaml configures auto_review to ignore PRs whose title contains that keyword.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

cicd

Poem

🐇 A [bump] in the title, a skip in the queue,
No rabbit reviews what the bots push through.
A YAML or two, a template rejigged,
The workflow hops on, with no review to be figged.
Less noise in the warren — hooray!

🚥 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 The PR title directly and clearly describes the main objective of the changeset: disabling CodeRabbit review on automated dependency bump pull requests by adding configuration to ignore them.
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.


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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 @.github/workflows/bump.yaml:
- Line 21: The title_template value on line 21 starts with a bracket character
that is being interpreted as YAML sequence syntax rather than a plain text
string. Quote the entire title_template value using either single or double
quotes to ensure the YAML parser treats it as a string literal instead of a
sequence, allowing the workflow file to be properly parsed.
🪄 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d0ecfa31-3519-493a-992a-2ae8d3be3ddf

📥 Commits

Reviewing files that changed from the base of the PR and between d69ba03 and 4c31b3e.

📒 Files selected for processing (2)
  • .coderabbit.yaml
  • .github/workflows/bump.yaml

Comment thread .github/workflows/bump.yaml Outdated
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
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