Skip to content

docs: distinguish file-path grouping types from prefix-only types - #90

Draft
beecave-orchestrator wants to merge 1 commit into
mainfrom
docs/clarify-commit-type-grouping-87
Draft

docs: distinguish file-path grouping types from prefix-only types#90
beecave-orchestrator wants to merge 1 commit into
mainfrom
docs/clarify-commit-type-grouping-87

Conversation

@beecave-orchestrator

Copy link
Copy Markdown
Collaborator

Update the module-level docstring in git_acp/git/classification.py to clarify that some commit types are selected by deterministic file-path grouping while others are prefix-only/heuristic.

Types with file-path grouping (via FILE_PATH_PATTERNS): DOCS, TEST, PERF, STYLE, BUILD, CI, CHORE.
Prefix-only types: FEAT, FIX, REFACTOR, REVERT.

Closes #87

Update the module-level docstring to clarify that DOCS, TEST, PERF, STYLE, BUILD, CI, and CHORE are selected via deterministic FILE_PATH_PATTERNS grouping, while FEAT, FIX, REFACTOR, and REVERT are prefix-only/heuristic types.

Closes #87
@coderabbitai

coderabbitai Bot commented Jul 5, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

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

Next review available in: 45 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 97c8430f-5314-4e41-b5bd-ac4f470744fb

📥 Commits

Reviewing files that changed from the base of the PR and between ed180ae and ba77e86.

📒 Files selected for processing (1)
  • git_acp/git/classification.py
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/clarify-commit-type-grouping-87

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.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs 📝: distinguish file-path grouping types from prefix-only types in module docstring

1 participant