[#569] Disable automatic CodeRabbit issue comments

[GodlyDonuts]

Why

CodeRabbit automatically enriches issues and generates full coding plans when common labels are applied, adding unsolicited noise to issue discussions. PR reviews and on-demand planning should remain available.

What

Closes: #569

• Disable automatic issue enrichment.
• Disable label-triggered issue planning.
• Preserve manually requested @coderabbitai plan functionality.
• Leave all PR review, status, chat, finishing-touch, and knowledge-base settings unchanged.

Test Plan

• pnpm exec prettier --check .coderabbit.yml
• Validated .coderabbit.yml against CodeRabbit’s live schema.v2.json

Checklist

• Database: No schema changes.
• Environment Variables: No environment variables changed.

[alexanderpaolini]

I'm not sure these are the choices we want to make @GodlyDonuts

Can you explain your reasoning for each of them?

I made this issue because the AI code review kept spamming edit suggestions, ai prompt suggestions, and pull request summaries, among other things. Honestly I already tried having ai silence coderabbit. It worked a bit, but not perfectly. So I made the issue to look at it more in depth when I have time.

Happy to look through this PR if you are willing to explain more in depth, but quite frankly I don't appreciate AI slop PRs without a real person describing the change produced.

[alexanderpaolini]

Also, @GodlyDonuts cosign your commits with the AI agent used in the future.

[GodlyDonuts]

@alexanderpaolini Thats my fault, I told codex to ignore the agents.md a while back and it seemed to have followed through with that command even now when creating this commit, including omitting the AI co-author trailer.

Okay so this is my justification for everything done:

• early_access: false: The issue planner is an early-access feature, so the idea was to prevent future spam from constantly changing early access features.
• issue_enrichment.auto_enrich: false: This prevents CodeRabbit from automatically adding its own generated context or analysis to issues.
• issue_enrichment.planning.enabled: false: This was to stop the large coding-plan comments like the one linked in CodeRabbit is still too spammy #569.
• issue_enrichment.planning.auto_planning.enabled: false: Ensure common labels such as Feature, Bug, and Onboarding no longer trigger those plans automatically.
• chat.auto_reply: false: Require someone to explicitly mention CodeRabbit before it joins a conversation.
• request_changes_workflow: false: Keep CodeRabbit’s review advisory rather than allowing it to participate in the formal approval/blocking workflow. This one is definitely out of scope from the issue.
• review_progress and commit_status: These were disabled to remove nonessential noise from PRs.
• auto_incremental_review: false: Avoid CodeRabbit posting another review every time someone pushes a follow-up commit. The initial review would remain enabled, and another review could still be requested manually.
• Docstring generation, unit-test generation, autofix, CI fixes, and conflict resolution were disabled because CodeRabbit exposes these as additional prompts and actions in its review comment.

My goal was to retain one quiet automatic code review when a PR leaves draft, while removing everything that creates unsolicited issue comments, repeated reviews, prompts, and extra status noise.

[GodlyDonuts]

@alexanderpaolini I realized that the solution could be a lot simpler than that, we could just do the following:

issue_enrichment:
  auto_enrich:
    enabled: false
  planning:
    enabled: true
    auto_planning:
      enabled: false

This would stop unsolicited comments and automatic coding plans like the one linked in #569, while preserving manually requested @coderabbitai plan functionality.

The existing configuration already uses the quiet review profile and disables PR summaries and AI-agent prompts, so this change should address the newly introduced issue spam without weakening the useful parts of CodeRabbit’s reviews. If that scope sounds right, I’ll amend the draft PR accordingly :)

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

if [ -f .coderabbit.yml ]; then
  nl -ba .coderabbit.yml | sed -n '1,260p'
else
  fd -HI '^\.coderabbit\.ya?ml$' .
fi

Length of output: 11817

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

nl -ba .coderabbit.yml | sed -n '249,380p'

Length of output: 4406

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

rg -n -C 8 '^\s*issue_enrichment:|^\s*(auto_enrich|planning|auto_planning):|^\s*enabled:\s*(true|false)\s*$' .coderabbit.yml | tail -n 150

Length of output: 3948

---

🤖 web_search executed:

CodeRabbit documentation issue_enrichment planning enabled auto_planning manual @coderabbitai plan early_access false

Length of output: 7469

---

@GodlyDonuts Change only Line 419:

issue_enrichment:
  auto_enrich:
    enabled: false
  planning:
    enabled: true
    auto_planning:
      enabled: false

This keeps manual @coderabbitai plan available and prevents automatic issue enrichment and label-triggered plans. The remaining configuration already disables the other PR noise sources.

---

✏️ Learnings added

Learnt from: GodlyDonuts
URL: https://github.com/KnightHacks/forge/pull/573

Timestamp: 2026-09-14T02:37:43.763Z
Learning: In `.coderabbit.yml`, retain manual GitHub Issue planning through `coderabbitai plan` by setting `issue_enrichment.planning.enabled: true`, while preventing unsolicited issue comments by setting `issue_enrichment.auto_enrich.enabled: false` and `issue_enrichment.planning.auto_planning.enabled: false`.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

You are interacting with an AI system.

[alexanderpaolini]

You are interacting with an AI system.

yeah bro I know

[GodlyDonuts]

You are interacting with an AI system.

yeah bro I know

mm lets add this as well so we can get rid of that:

knowledge_base:
  opt_out: true

[ChrisH0125]

@GodlyDonuts IMO a lot of these changes are unnecessary but I like the more narrow version that you just put out. Personally, these are my critiques and what doesn't need to be changed or altered that much unless everyone says otherwise:

• auto_incremental_review (This is becuz it can still provide useful reviews and we don't need to manually just ping coderabbit for these changes) so like completely stopping it for new commits can be a little annoying
• request_changes_workflow (you already said it was oos so it's chill) but yea
• review_progress - I think this change is also not needed since the main issue is just reducing clutterness from coderabbit and not spam with long code suggestions. The review progress is separate from the commentary part I believe. It is still useful to have these checks so we can make sure it is finished with review :p
• ^ commit_status same thing
• early_access - I don't get this one at all tbh nor the explanation of it, if we disable this. What happens? What early access features will it like opt out of or disable and why? Doesn't seem inherently bad, just want more clarification lol

Rest of it seems fine with me to reduce some AI clutter, especially with the enrichment changes

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: QUIET

Plan: Advanced

Run ID: 3168ce70-ad88-45f6-a857-d946ed86e165

📥 Commits

Reviewing files that changed from the base of the PR and between 97b93c3 and b515408.

📒 Files selected for processing (1)

• .coderabbit.yml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The CodeRabbit configuration disables issue_enrichment.auto_enrich and planning.auto_planning. It removes the automatic planning labels. planning.enabled remains enabled.

Priority: ➖ Normal

Severity of issue fixed: Medium

Merge Risk: ⚪ Minimal · up to b5154

The change limits unsolicited automation while preserving manual planning and review workflows.

🚥 Pre-merge checks | ✅ 8

✅ Passed checks (8 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Issue #569 requires less unsolicited CodeRabbit issue and pull-request activity while retaining useful AI reviews. This change disables issue_enrichment.auto_enrich and `issue_enrichment.planning.au…
Out of Scope Changes check	✅ Passed	The diff changes only .coderabbit.yml issue-enrichment and automatic-planning settings. These changes directly support issue #569 by reducing unsolicited CodeRabbit activity. No unrelated change is …
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
No Hardcoded Secrets	✅ Passed	No hardcoded secret was introduced. The pull request changes only .coderabbit.yml and adds enabled: false values. No added line contains an API key, password, token, or secret literal.
Validated Env Access	✅ Passed	No new direct process.env usage was introduced. The PR changes only .coderabbit.yml, and its diff contains no process.env access. Base and head have the same existing occurrences; the changed co…
No Typescript Escape Hatches	✅ Passed	The pull request changes only .coderabbit.yml. Added lines contain only enabled: false; no TypeScript files or usages of any, @ts-ignore, @ts-expect-error, or !. were introduced.
Title check	✅ Passed	The title starts with [#569], describes disabling automatic CodeRabbit issue comments, and is 50 characters long.
Description check	✅ Passed	The description explains the configuration changes and the reason for disabling automatic issue enrichment and label-triggered planning.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}