Skip to content

chore: enable repo automation (CodeRabbit + release-please) - #158

Merged
fatblaine merged 4 commits into
mainfrom
dev
Aug 4, 2026
Merged

fatblaine merged 4 commits into
mainfrom
dev

Conversation

@fatblaine

Copy link
Copy Markdown
Owner

What

Promote the repo-automation config from dev to production (main), per docs/planning/repo-automation-plan.md sections B1 + C:

  • CodeRabbit — automated AI review on every PR (.coderabbit.yaml)
  • release-please — automated versioning, CHANGELOG.md, and GitHub Releases from Conventional Commits

Why

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

File Purpose
.coderabbit.yaml chill profile, English reviews, auto-review on dev/main, path-scoped instructions aligned to CLAUDE.md (backend/frontend/agent)
.github/release-please-config.json simple release-type, single app version, changelog-sections mapping commit types → sections
.github/.release-please-manifest.json Current version pinned to 1.0.0 (auto-maintained after this)
.github/workflows/release-please.yml Runs on push to main, opens/maintains the Release PR

Activation

Merging this into main is what first activates the release-please workflow (on: push: branches: [main]).

Before/after merge, confirm:

  • Settings → Actions → General → Read and write permissions + Allow GitHub Actions to create and approve pull requests are enabled
  • Settings → General → Pull Requests → squash default commit message set to "Pull request title" (keeps squash merges Conventional-Commits compliant)

Verification

  • After merge, an empty green release-please run appears in Actions — no Release PR yet, since every commit since v1.0.0 is chore: (expected, not a failure).
  • Next feat:/fix: reaching main auto-opens a chore(main): release suburblens 1.x.0 PR with a generated CHANGELOG; merging that PR tags the release.

Notes

  • Config only — no production code touched.
  • CLAUDE.md and docs/planning/ai-changelog.md were updated alongside this work but are gitignored, so they're not in the diff.

@fatblaine
fatblaine requested a review from Copilot August 4, 2026 01:02
@fatblaine fatblaine self-assigned this Aug 4, 2026
@fatblaine fatblaine added documentation Improvements or additions to documentation enhancement New feature or request labels Aug 4, 2026
@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@fatblaine, you've reached your PR review limit, so we couldn't start this review.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 111edbb1-6eb7-47a4-998f-ec3acada1497

📥 Commits

Reviewing files that changed from the base of the PR and between 02d14cf and 9345aaf.

📒 Files selected for processing (4)
  • .coderabbit.yaml
  • .github/.release-please-manifest.json
  • .github/release-please-config.json
  • .github/workflows/release-please.yml

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

Comment @coderabbitai help to get the list of available commands.

@fatblaine
fatblaine merged commit 8f453a2 into main Aug 4, 2026
9 checks passed

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-please GitHub Actions workflow that runs on pushes to main.
  • Introduce release-please configuration + manifest to define release behavior and starting version.
  • Add CodeRabbit configuration for auto-review on dev/main with 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.

Comment on lines +7 to +11
permissions:
contents: write
pull-requests: write

jobs:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants