chore: disable CodeRabbit review status

[arendjr]

Summary

Let's see if this works :)

cc @ematipico

Test Plan

Watch the rabbit.

Docs

N/A

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4b0b7a0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The pull request updates .coderabbit.yaml by changing the reviews.review_status flag from true to false. No other configuration entries are modified, and there are no changes to exported or public APIs.

Possibly related PRs

• chore: apply CodeRabbit nits #7116: Also modifies the reviews section of .coderabbit.yaml by adding two boolean options.
• chore: add CodeRabbit config #7114: Introduces .coderabbit.yaml with review_status enabled; this PR flips that same setting to false.

Suggested reviewers

• ematipico
• dyc3

Pre-merge checks (2 passed, 1 inconclusive)

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	❓ Inconclusive	The current description relies on casual placeholders and does not detail the actual change to the review_status flag in .coderabbit.yaml, making it too vague to inform reviewers of what was modified. While it references CodeRabbit, it fails to outline the specific configuration update being applied.	Please update the description to clearly summarise that the review_status flag in .coderabbit.yaml was toggled from true to false to disable CodeRabbit reviews and include any relevant context.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly describes the core change by indicating that the CodeRabbit review status is being disabled, which precisely matches the single modification in .coderabbit.yaml. It also follows conventional commit style conventions and avoids unnecessary detail, making it clear and actionable.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.coderabbit.yaml (1)

8-8: Optional: Silence commit statuses too

If you also want zero GitHub “checks” noise, flip commit_status to false.

-  commit_status: true
+  commit_status: false

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between aa06833 and 4b0b7a0.

📒 Files selected for processing (1)

• .coderabbit.yaml (1 hunks)

🔇 Additional comments (1)

.coderabbit.yaml (1)

10-10: Review status disabled — LGTM

Per schema, setting reviews.review_status: false stops posting review details and the “skipped” status comment. Looks aligned with the PR intent.