Add CodeRabbit configuration

[sradco]

Add .coderabbit.yaml with:

• Path filters to skip review of generated
  dashboard YAMLs (dashboards/perses/**)
  and go.sum
• Review instruction for Go files to flag
  functions that are too long and should be
  split into smaller, focused helpers

Signed-off-by: Shirly Radco sradco@redhat.com
Co-authored-by: AI Assistant noreply@cursor.com

Made with Cursor

[coderabbitai]

Warning

Review limit reached

@sradco, we couldn't start this review because you've used your available PR reviews for now.

Your plan includes 1 review of capacity. Refill in 43 minutes and 57 seconds.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more review capacity refills, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 758a46c4-6ac9-4c04-ba59-0ce9e18525ea

📥 Commits

Reviewing files that changed from the base of the PR and between ff70c50 and a79023d.

📒 Files selected for processing (3)

• .coderabbit.yaml
• docs/review_guidelines/dashboards.md
• docs/review_guidelines/go.md

📝 Walkthrough

Walkthrough

This PR adds Go-specific review guidance (docs/review_guidelines/go.md), extends dashboard review instructions with Grafana and Perses guidance (docs/review_guidelines/dashboards.md), and updates .coderabbit.yaml to exclude go.sum from path_filters and to direct Go files (**/*.go) to the new Go review guidelines.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• kubevirt/hyperconverged-cluster-operator#4246: Both PRs touch CodeRabbit configuration and Go review guidance.
• kubevirt/monitoring#374: Prior update to CodeRabbit/dashboard review guidance in this repository.

---

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 and usage tips.}

[avlitman]

can this be maybe under docs/review_guidelines/go.md?

[sradco]

Fixed. Thanks

[coderabbitai]

🧹 Nitpick comments (1)

docs/review_guidelines/go.md (1)

5-9: ⚡ Quick win

Clarify scope and exceptions to reduce subjective enforcement.

These rules are directionally good, but “~30 lines” and “hard to understand at a glance” are still ambiguous. Please add brief qualifiers (for example: exclude test helpers/generated code, and call out acceptable anonymous-function use such as short go func closures) so reviewers apply this consistently.

[Suggestion example]

Proposed wording

-- Keep functions short and focused. A function longer than ~30 lines
-  is a signal to split it.
+- Keep functions short and focused. In production code, a function longer
+  than ~30 non-comment lines is a signal to split it (tests and generated
+  code may be exceptions).
...
-- Flag any function that is hard to understand at a glance.
+- Flag any function that is hard to understand quickly due to mixed concerns,
+  deep nesting, or unclear naming.

As per coding guidelines, “confirm the doc is understandable by cluster administrators who aren’t Go developers.”

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/review_guidelines/go.md` around lines 5 - 9, Update the guidance text to
remove ambiguity by adding brief qualifiers: state that the "~30 lines"
guideline is directional (not a hard limit) and should exclude test helpers and
generated code; clarify that "each function should do one thing" allows short,
idiomatic anonymous functions (e.g., brief go func closures, inline callbacks
under ~10 lines) and utility lambdas, and add a note that reviewers should flag
only functions that are long/complex enough to harm readability or maintenance
for cluster administrators unfamiliar with Go; reference the existing bullets
about function length and anonymous functions so reviewers apply these
exceptions consistently.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@docs/review_guidelines/go.md`:
- Around line 5-9: Update the guidance text to remove ambiguity by adding brief
qualifiers: state that the "~30 lines" guideline is directional (not a hard
limit) and should exclude test helpers and generated code; clarify that "each
function should do one thing" allows short, idiomatic anonymous functions (e.g.,
brief go func closures, inline callbacks under ~10 lines) and utility lambdas,
and add a note that reviewers should flag only functions that are long/complex
enough to harm readability or maintenance for cluster administrators unfamiliar
with Go; reference the existing bullets about function length and anonymous
functions so reviewers apply these exceptions consistently.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 0bc8a7cc-a53a-4f10-a99d-d3aa82022445

📥 Commits

Reviewing files that changed from the base of the PR and between ac35d10 and ff70c50.

📒 Files selected for processing (3)

• .coderabbit.yaml
• docs/review_guidelines/dashboards.md
• docs/review_guidelines/go.md

✅ Files skipped from review due to trivial changes (2)

• docs/review_guidelines/dashboards.md
• .coderabbit.yaml

[sradco]

@avlitman update, please review