Add coderabbit config

[i7an]

Motivation

Automate leaked credentials identification.

Changes

• Added code rabbit config with instructions

Summary by CodeRabbit

• Chores
  • Added/updated code review tooling configuration to specify language, schema, and automated guidance for reviewing test fixture files for sensitive data.

Note: This release contains only internal tooling updates with no end-user visible changes.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Warning

Rate limit exceeded

@i7an has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 3 minutes and 43 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, 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 the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📝 Walkthrough

Walkthrough

Adds a new CodeRabbit configuration file (.coderabbit.yaml) specifying English, a yaml-language-server schema reference, and path-specific data-privacy review instructions for VCR cassette files under spec/fixtures/vcr_cassettes/**/*.yml.

Changes

Cohort / File(s)	Summary
CodeRabbit Configuration \.coderabbit\.yaml	New YAML configuration added with yaml-language-server schema reference, language: English, path_instructions for spec/fixtures/vcr_cassettes/**/*.yml, and an instruction to act as a data privacy officer to identify sensitive data (PII, credentials) while ignoring obvious placeholders.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 I hopped in with a YAML song,
Guarding cassettes the whole day long,
I sniff for secrets, PII in view,
Tucking credentials where none slip through,
A tiny rabbit keeping data strong.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add coderabbit config' directly reflects the main change—adding a configuration file for CodeRabbit—and is concise and specific.
Description check	✅ Passed	The description includes motivation and changes sections but omits 'How to test' and 'Images and GIFs' sections required by the template.
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.}

---

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

[DagonWat]

I will re-base one of my branches to see how/if it works correctly

[DagonWat]

@i7an I think that coderabbit actually picked up some sensitive data usecase in this PR - #81, even though I think its a bit noisy and in this case useless... Maybe we should discuss it