chore(coderabbit): enable auto-review on PRs targeting dev

[Artic0din]

Summary

Add dev to .coderabbit.yaml auto_review.base_branches so feature PRs against dev get CR review without manual @coderabbitai review trigger.

What was broken

PR #64 (Phase 3.1 ranking foundation) opened against dev and CR auto-skipped:

Auto reviews are disabled on base/target branches other than the default branch.

The current base_branches list is [main, develop]. PriceHawk uses dev as the integration branch (per the v1.4 → v1.5 stack pattern), so every feature PR has hit this same wall.

What this fixes

Future feature PRs targeting dev get CR review immediately. No more manual trigger overhead. The main and develop entries stay so behavior is purely additive.

Test plan

• python -c "import yaml; yaml.safe_load(open('.coderabbit.yaml'))" passes
• Diff is +1 line under existing auto_review.base_branches — no schema change
• Validates by CR running on this PR itself (this PR targets dev so it's the canary)

Changes

Single line addition:

   base_branches:
     - "main"
     - "develop"
+    - "dev"

Why

PriceHawk's branch model is feat/* → dev → main. Without dev in the auto-review allowlist, every feature PR sits unreviewed until someone manually triggers CR.

Breaking Changes

None. Additive yaml change. CR re-reads .coderabbit.yaml on next PR event.

Files Changed

• .coderabbit.yaml (+1 line)

🤖 Generated with Claude Code

Summary by Sourcery

Build:

• Update .coderabbit.yaml to include dev in the auto_review.base_branches list so PRs into dev receive automatic reviews.

Changes

• Updated CodeRabbit auto-review configuration to include "dev" in the auto_review.base_branches list, alongside the existing "main" and "develop" entries
• Rationale: PriceHawk's primary integration branch is dev. Previously, PRs opened against dev were auto-skipped by CodeRabbit because dev was not in the base_branches configuration, requiring manual trigger (@coderabbitai review). This change enables automatic code review for future feature PRs targeting the dev branch without manual intervention.

Files Changed

File	Lines Added	Lines Removed
.coderabbit.yaml	1	0

Breaking Changes

None. This is an additive configuration change that does not alter existing behavior for the "main" and "develop" branches.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the CodeRabbit configuration to automatically trigger reviews on pull requests targeting the dev branch, in addition to main and develop.

File-Level Changes

Change	Details	Files
Enable CodeRabbit auto-reviews for PRs targeting the dev branch.	Add dev to the auto_review.base_branches list under the reviews configuration. Keep existing main and develop entries unchanged to preserve current behavior. Ensure YAML structure and schema remain the same with only a single-line additive change.	.coderabbit.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 1a3ca352-5628-49cc-a717-2d92e6c06223

📥 Commits

Reviewing files that changed from the base of the PR and between cc6a386 and d4d7ffc.

📒 Files selected for processing (1)

• .coderabbit.yaml

📜 Recent review details

🔇 Additional comments (1)

.coderabbit.yaml (1)

60-60: LGTM!

---

Walkthrough

The PR updates the CodeRabbit review configuration to enable auto-reviews on the dev branch in addition to existing main and develop branch targets.

Changes

Configuration Update

Layer / File(s)	Summary
Auto-review base branches configuration .coderabbit.yaml	Added "dev" to the reviews.auto_review.base_branches list, expanding auto-review targeting to three branches.

---

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: enabling CodeRabbit auto-review for PRs targeting the dev branch.
Description check	✅ Passed	The description covers all essential information: what changed, why it was needed, test validation, and impact. However, the Type checkbox and some Documentation checkboxes were not explicitly marked.
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.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/coderabbit-enable-dev-base

• 🛠️ scrub-secrets
• 🛠️ no-hardcoded-rates
• 🛠️ amber-api-limits
• 🛠️ dashboard-protocol-safety

---

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

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}