Add configuration for coderabbit

[JoelSpeed]

Based on the configuration reference, this is an attempt to quieten coderabbit down to exactly the useful content we want.

This includes:

• Disabling walkthrough as much as possible, this doesn't appear useful to reviewers
• Preferring local learnings - this repo acts very differently to others
• Ignoring changes in vendor
• Ignoring changes to some generated files
• Specifically requesting it use our AGENTS.md file

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new .coderabbit.yaml configuration file. It sets language: en-US; review options with profile: "chill", high_level_summary: false, review_status: true, commit_status: true, collapse_walkthrough: true, changed_files_summary: false, sequence_diagrams: false, estimate_code_review_effort: false, poem: false, and suggested_labels: false. Enables golangci-lint under tools. Defines path_filters excluding payload-manifests, zz_generated.crd-manifests/*, zz_generated.featuregated-crd-manifests/**, and vendor/**. knowledge_base enables code_guidelines from AGENTS.md with learnings.scope: local.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a configuration file for coderabbit.
Description check	✅ Passed	The description is directly related to the changeset, explaining the rationale and specific configuration options being added to the .coderabbit.yaml file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

[openshift-ci]

Hello @JoelSpeed! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between e2f22b7 and f2de708.

📒 Files selected for processing (1)

• .coderabbit.yaml

🔇 Additional comments (2)

.coderabbit.yaml (2)

1-24: Configuration aligns well with PR objectives.

The settings appropriately reduce noise by:

• Disabling high-level summaries, changed files summaries, sequence diagrams, and label suggestions (lines 4, 8–11).
• Collapsing the walkthrough into a collapsible section (line 7).
• Preferring local learnings for this repository (line 24).
• Explicitly using AGENTS.md for code guidelines (line 22).
• Excluding vendor and generated manifests from reviews (lines 13–17, pending fix above).

Once the two issues above are resolved, the configuration should effectively achieve the stated goals.

---

16-17: Path filter syntax error: missing negation prefix.

Line 17 specifies vendor/** without the ! prefix. Unlike line 16 (!vendor/**), this will include vendor directories instead of excluding them, contradicting the PR objective to ignore vendor changes. Remove line 17 or correct it to match line 16.

🔎 Proposed fix

  - "!**/zz_generated.featuregated-crd-manifests/**" # Contains folders
- - "!vendor/**"
- - "vendor/**"
+ - "!vendor/**"

Likely an incorrect or invalid review comment.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.coderabbit.yaml (1)

17-18: Consider removing redundant vendor pattern.

Both !**/vendor/** and !vendor/** are specified. The pattern !**/vendor/** matches vendor directories at any level (including the root), making !vendor/** redundant.

🔎 Proposed simplification

  - "!**/zz_generated.featuregated-crd-manifests/**" # Contains folders
  - "!**/vendor/**"
- - "!vendor/**"

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between f2de708 and dc5f7e0.

📒 Files selected for processing (1)

• .coderabbit.yaml

🔇 Additional comments (4)

.coderabbit.yaml (4)

1-1: LGTM!

The language setting is correctly configured.

---

2-16: LGTM!

The review configuration correctly disables unnecessary features to reduce noise as intended. All settings are valid according to the schema and align with the PR objectives.

---

19-21: LGTM!

The golangci-lint tool is correctly enabled for Go code analysis.

---

22-28: LGTM!

The knowledge base configuration correctly enables code guidelines from AGENTS.md and sets learnings scope to local, aligning with the PR objectives to use repository-specific guidelines and prefer local learnings.

[yuqi-zhang]

lgtm based on the documentation. A few fields (profile, review_status, commit_status) seem to be their default values. Did you mean to explicitly set those as well?

[JoelSpeed]

A few fields (profile, review_status, commit_status) seem to be their default values. Did you mean to explicitly set those as well?

Yes. I was intending to be explicit about the choices rather than relying on defaults, even though these are the defaults

[yuqi-zhang]

/lgtm

[JoelSpeed]

/approve
/override ci/prow/okd-scos-images

[openshift-ci]

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/okd-scos-images

Details

In response to this:

/approve
/override ci/prow/okd-scos-images

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.

[openshift-ci]

@JoelSpeed: 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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, yuqi-zhang

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 [JoelSpeed]

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