Skip to content

docs: clarify allow_branch_types defaults are a superset of the spec - #509

Merged
shenxianpeng merged 1 commit into
mainfrom
docs/sync-branch-type-docs
Aug 1, 2026
Merged

docs: clarify allow_branch_types defaults are a superset of the spec#509
shenxianpeng merged 1 commit into
mainfrom
docs/sync-branch-type-docs

Conversation

@shenxianpeng

Copy link
Copy Markdown
Member

Summary

Follow-up to #505 (merged). Two documentation cleanups requested during review:

  1. Fix the review comment on feat: allow docs, ci, test, refactor branches by default #505 — the options table in docs/configuration.rst listed only 14 of the 21 default branch types and omitted ai, claude, codex, copilot, cursor, dependabot, renovate from the Default column. The Default column now lists the full DEFAULT_BRANCH_TYPES list.

  2. Make the spec deviation explicitDEFAULT_BRANCH_TYPES is a superset of the Conventional Branch spec: spec types (feature, bugfix, hotfix, release, chore) plus Conventional Commit types (build, ci, docs, perf, refactor, style, test) and AI/bot prefixes (ai, claude, codex, copilot, cursor, dependabot, renovate). The description column and both config examples (README + docs/configuration.rst) now state this explicitly, and point users to allow_branch_types for strict spec-only validation.

Changes

  • README.md — comment above allow_branch_types in the example config
  • docs/configuration.rst — full default list in the Options table; expanded description with spec-superset note; example config reformatted to match the README (multi-line) with a clarifying comment

Validation

  • sphinx-build -E -b html docs _build/html succeeds; no new warnings (existing 7 warnings are pre-existing in changelog.rst/migration.rst)
  • Options table renders all 21 default types

Closes #494

Addresses the review comment on #505: the options table now lists the full
default (all 21 types including AI agent and bot prefixes) and the docs
explicitly note that DEFAULT_BRANCH_TYPES is a superset of the Conventional
Branch spec, with strict spec-only validation available via an explicit
allow_branch_types setting.

Closes #494
@shenxianpeng
shenxianpeng requested a review from a team as a code owner August 1, 2026 20:49
@netlify

netlify Bot commented Aug 1, 2026

Copy link
Copy Markdown

Deploy Preview for commit-check ready!

Name Link
🔨 Latest commit bf00f79
🔍 Latest deploy log https://app.netlify.com/projects/commit-check/deploys/6a6e5be3d9445200084b9e3d
😎 Deploy Preview https://deploy-preview-509--commit-check.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai

coderabbitai Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

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

Next review available in: 52 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1f1f902a-a869-4f7d-ab72-b9e71709886d

📥 Commits

Reviewing files that changed from the base of the PR and between 0ce5695 and bf00f79.

📒 Files selected for processing (2)
  • README.md
  • docs/configuration.rst

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.

@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Aug 1, 2026
@sonarqubecloud

sonarqubecloud Bot commented Aug 1, 2026

Copy link
Copy Markdown

@shenxianpeng
shenxianpeng merged commit 36880d0 into main Aug 1, 2026
12 checks passed
@shenxianpeng
shenxianpeng deleted the docs/sync-branch-type-docs branch August 1, 2026 20:52
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow docs/, ci/, test/, refactor/ branches by default

1 participant