Skip to content

Switch CodeRabbit to assertive profile via committed .coderabbit.yaml #10613

Description

@dblythy

New Feature / Enhancement Checklist

Current Limitation

CodeRabbit currently reviews with the default chill profile (visible in the review details on recent PRs, e.g. #10610), and its configuration lives only in the CodeRabbit dashboard. There's no .coderabbit.yaml in the repo, so the active settings aren't visible, versioned or reviewable by contributors.

Feature / Enhancement Description

Switch CodeRabbit to the assertive profile and commit the configuration as a .coderabbit.yaml:

  • profile: assertive for more thorough feedback - as a security-sensitive server with a small maintainer team, catching more in automated review is worth the extra noise
  • replicate the existing dashboard settings (custom pre-merge checks like "Engage In Review Feedback" and "Security Check") into the file, since a committed .coderabbit.yaml takes precedence over the dashboard
  • path_instructions for src/**, spec/** and the generated types/*.d.ts
  • auto_review filters to skip draft and dependabot PRs

Example Use Case

  1. A contributor opens a PR and gets deeper automated review before a maintainer spends time on it
  2. A contributor wants to know why CodeRabbit flagged something and opens .coderabbit.yaml to see the active profile and rules
  3. Changes to review behaviour go through a PR like any other change

Alternatives / Workarounds

  • Flip the profile in the dashboard without committing config. Less friction, but settings stay invisible and untracked.
  • Stay on chill (current state).

3rd Party References

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions