Conversation
chore: add CodeRabbit config
chore: add release-please automation config
|
Warning Review limit reached
Next review available in: 53 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
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 |
There was a problem hiding this comment.
Pull request overview
Promotes repository automation configuration to production (main) by enabling CodeRabbit automated PR reviews and adding release-please for Conventional Commits–driven release PRs, changelog generation, and GitHub Releases.
Changes:
- Add
release-pleaseGitHub Actions workflow that runs on pushes tomain. - Introduce release-please configuration + manifest to define release behavior and starting version.
- Add CodeRabbit configuration for auto-review on
dev/mainwith path-scoped guidance.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
.github/workflows/release-please.yml |
Adds the release-please automation workflow triggered on pushes to main. |
.github/release-please-config.json |
Configures release-please release type and changelog section mapping. |
.github/.release-please-manifest.json |
Pins initial release-please manifest version (1.0.0). |
.coderabbit.yaml |
Enables CodeRabbit auto-review with path-specific review instructions. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| permissions: | ||
| contents: write | ||
| pull-requests: write | ||
|
|
||
| jobs: |
What
Promote the repo-automation config from
devto production (main), perdocs/planning/repo-automation-plan.mdsections B1 + C:.coderabbit.yaml)CHANGELOG.md, and GitHub Releases from Conventional CommitsWhy
Solo repo with no second reviewer and manual releases. CodeRabbit fills the review gap; release-please turns "hand-write release notes + tag" into "merge one auto-generated Release PR". Both zero-cost, no change to the feat→dev→main flow.
Changes
.coderabbit.yamlchillprofile, English reviews, auto-review ondev/main, path-scoped instructions aligned to CLAUDE.md (backend/frontend/agent).github/release-please-config.jsonsimplerelease-type, single app version, changelog-sections mapping commit types → sections.github/.release-please-manifest.json1.0.0(auto-maintained after this).github/workflows/release-please.ymlmain, opens/maintains the Release PRActivation
Merging this into
mainis what first activates the release-please workflow (on: push: branches: [main]).Before/after merge, confirm:
Verification
release-pleaserun appears in Actions — no Release PR yet, since every commit since v1.0.0 ischore:(expected, not a failure).feat:/fix:reachingmainauto-opens achore(main): release suburblens 1.x.0PR with a generated CHANGELOG; merging that PR tags the release.Notes
CLAUDE.mdanddocs/planning/ai-changelog.mdwere updated alongside this work but are gitignored, so they're not in the diff.