fix: remove problematic CodeRabbit config settings

[MitaliBhalla]

Fixes issues in the recently merged CodeRabbit config (#894):

• Remove auto_title_placeholder: "CodeRabbit" — This setting unintentionally triggers title replacement on any PR containing "coderabbit" (case-insensitive), including the original PR itself
• Remove unused linear section — We don't use Linear; keeping empty placeholders adds noise

No functional changes to review behavior.

Made with Cursor

Summary by CodeRabbit

• Chores
  • Updated the auto-generated review title placeholder to show "@coderabbitai" instead of the previous value.
  • Removed an unused/empty knowledge base configuration entry.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 60785084-fa70-43f9-a3fe-27951428e23e

📥 Commits

Reviewing files that changed from the base of the PR and between b4f5fc9 and 75150f3.

📒 Files selected for processing (1)

• .coderabbit.yaml

🚧 Files skipped from review as they are similar to previous changes (1)

• .coderabbit.yaml

---

Walkthrough

Updated .coderabbit.yaml: changed reviews.auto_title_placeholder from "CodeRabbit" to "@coderabbitai" and removed the empty knowledge_base.linear.team_keys entry. (34 words)

Changes

Cohort / File(s)	Summary
Configuration file .coderabbit.yaml	Modified reviews.auto_title_placeholder value from "CodeRabbit" → "@coderabbitai"; removed knowledge_base.linear.team_keys: [].

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: removing problematic CodeRabbit configuration settings from .coderabbit.yaml, which aligns with both the auto_title_placeholder update and the removal of the unused linear section.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[krishvoor]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: krishvoor, MitaliBhalla

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [MitaliBhalla]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@MitaliBhalla: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 53.96%. Comparing base (a2f75c7) to head (75150f3).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #922      +/-   ##
==========================================
+ Coverage   53.93%   53.96%   +0.03%     
==========================================
  Files          88       88              
  Lines        6656     6656              
==========================================
+ Hits         3590     3592       +2     
+ Misses       2596     2595       -1     
+ Partials      470      469       -1     

see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.