adding coderabbit config

[acornett21]

Summary by CodeRabbit

• Chores
  • Added repository-wide code review automation configuration to streamline development workflows and enforce test quality standards.

[coderabbitai]

Walkthrough

A new .coderabbit.yaml file configures CodeRabbit repository settings: English locale, review toggles, path filters to exclude vendor and generated content, auto-review for drafts, and pre-merge custom checks enforcing Ginkgo test name stability and quality standards.

Changes

CodeRabbit Configuration

Layer / File(s)	Summary
Core configuration and path filtering .coderabbit.yaml	English locale, review toggles (high-level summaries, status, walkthrough display), path filters to exclude vendor/generated/boilerplate content, and auto-review enabled for drafts.
Pre-merge quality checks and feature toggles .coderabbit.yaml	Error-level custom check enforces deterministic Ginkgo test names by rejecting dynamic identifiers (timestamps, UUIDs, node names). Warning-level check documents expected Ginkgo test structure (single responsibility, proper setup/cleanup, timeouts, assertion clarity, codebase consistency). Chat auto-reply is enabled; art feature is disabled.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 7

✅ Passed checks (7 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'adding coderabbit config' accurately describes the main change in the pull request, which is the addition of a .coderabbit.yaml configuration file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PR adds only configuration files and suite setup (no test blocks). The only test file (suite_test.go) contains BeforeSuite/AfterSuite but zero It/Describe/Context test blocks with titles to validate.
Test Structure And Quality	✅ Passed	PR only adds .coderabbit.yaml configuration file; no Ginkgo test code files were modified, making the test quality check inapplicable to this PR.

_{✏️ 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.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.coderabbit.yaml (1)

84-84: ⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove the stray root scalar to fix YAML parsing.

Line 84 contains a standalone 84, which makes this document invalid YAML (mapping + bare scalar at root). This will likely prevent CodeRabbit from loading the config.

Suggested fix

 chat:
   auto_reply: true
   art: false
-84

🤖 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 @.coderabbit.yaml at line 84, Remove the stray root scalar "84" that was left
alone in the YAML document (the standalone scalar at the document root), which
breaks parsing; locate the bare value "84" and either delete that line or
incorporate it properly into the existing mapping/sequence (e.g., as a key:value
entry under the appropriate mapping) so the file is valid YAML again.

🤖 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.

Outside diff comments:
In @.coderabbit.yaml:
- Line 84: Remove the stray root scalar "84" that was left alone in the YAML
document (the standalone scalar at the document root), which breaks parsing;
locate the bare value "84" and either delete that line or incorporate it
properly into the existing mapping/sequence (e.g., as a key:value entry under
the appropriate mapping) so the file is valid YAML again.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: f3a09692-21c3-42a3-998b-48d9f6b821d0

📥 Commits

Reviewing files that changed from the base of the PR and between e21ac64 and 39558f1.

📒 Files selected for processing (1)

• .coderabbit.yaml