Point Renovate and CodeRabbit at release/v5 - #264
Conversation
Every pull request in this repository targets release/v5, but GitHub's default branch is main. Both tools read the default branch and act on it unless told otherwise, so both were pointed at a branch nobody develops on. CodeRabbit had already stopped reviewing. It posts a comment saying auto reviews are disabled for base branches other than the default rather than failing a check, so pull requests merge unreviewed and nothing goes red. Renovate's pull requests have been landing on release/v5, but that is inherited from when it was the default branch, not from anything written down. The next time Renovate resolves the default it would open against main instead, where the changes would sit unmerged. Neither setting takes effect until it reaches the default branch, since that is where both tools read their configuration. Co-Authored-By: Claude Code <[email protected]>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe PR adds CodeRabbit and Renovate configuration. Both tools target the ChangesRelease branch automation
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This change directs CodeRabbit reviews and Renovate updates to release/v5 without changing the repository default branch. The configuration matches the intended branch targeting and is ready to merge. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Every pull request in this repository targets
release/v5, but GitHub's default branch ismain.Renovate and CodeRabbit both read the default branch and act on it unless told otherwise, so both
were pointed at a branch nobody develops on.
CodeRabbit had already stopped reviewing
It posts a comment rather than failing a check:
So pull requests merge unreviewed and nothing goes red.
.coderabbit.yamladdsrelease/v5toreviews.auto_review.base_branches. The default branch stays covered automatically, so this addsrelease/v5rather than replacing anything.Renovate was working by inheritance, not by configuration
Its pull requests have been landing on
release/v5, but nothing in the repository says they should.That behaviour is left over from when
release/v5was the default branch. The next time Renovateresolves the default it opens against
maininstead, where dependency updates would sit unmergedwhile
release/v5quietly goes stale.baseBrancheswrites the intent down.When each takes effect
They differ, and the difference was measured on this pull request rather than assumed.
CodeRabbit reads
.coderabbit.yamlfrom the branch. It picked this file up from the head ofthis pull request and reviewed it, on a
release/v5base, before anything merged. Its own runconfiguration reports
Configuration used: Path: .coderabbit.yaml. So that half is live already.Renovate reads its configuration from the default branch.
baseBranchestherefore does nothinguntil it reaches
main, and the sync fromrelease/v5is what activates it.The alternative was changing GitHub's default branch to
release/v5, which fixes both tools withone setting. It was not taken because a setting that is invisible in the repository is what caused
this: reading the branch topology alone suggested
release/v5was a stale release line, when it iswhere all the work happens.