Skip to content

chore: switch to inherited org-level config from commit-check/.github#223

Merged
shenxianpeng merged 2 commits into
mainfrom
chore/use-inherited-org-config
Jun 26, 2026
Merged

chore: switch to inherited org-level config from commit-check/.github#223
shenxianpeng merged 2 commits into
mainfrom
chore/use-inherited-org-config

Conversation

@shenxianpeng

@shenxianpeng shenxianpeng commented Jun 26, 2026

Copy link
Copy Markdown
Member

Summary

Replace the standalone commit-check.toml with a minimal config that uses the organization-level base configuration via:

inherit_from = "github:commit-check/.github:commit-check.toml"

Only the action-repo-specific require_rebase_target = "origin/main" is kept locally.

Changes

Before After
20 lines of duplicated config 3 lines, inherits from org-level
Manually maintained in sync with org Automatically inherits updates

Benefits

Verification

The org config covers all previously local settings with minor improvements (e.g., additional ignore_authors entries for coderabbitai[bot] and shenxianpeng).

@shenxianpeng shenxianpeng requested a review from a team as a code owner June 26, 2026 21:41
@coderabbitai

coderabbitai Bot commented Jun 26, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

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

More reviews will be available in 51 minutes and 4 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 05a69e58-2325-4bfe-937d-24d79cf41504

📥 Commits

Reviewing files that changed from the base of the PR and between 275f4d9 and 84ca51a.

📒 Files selected for processing (2)
  • commit-check.toml
  • main.py
📝 Walkthrough

Walkthrough

The commit-check configuration now inherits a shared base file. The local file keeps only the branch rebase-target override and removes the inline commit validation settings.

Changes

Shared commit-check configuration

Layer / File(s) Summary
Inheritance and branch override
commit-check.toml
The config now inherits github:commit-check/.github:commit-check.toml and retains require_rebase_target = "origin/main" under [branch].

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 I hop through config, neat and light,
Shared base in place, all tidy right.
One branch rule stays, the rest take flight,
Boing! The checks now read just right.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly matches the main change: switching to inherited org-level commit-check config.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/use-inherited-org-config

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 commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Commit-Check ✔️

Replace the standalone commit-check.toml with a minimal config that
inherits from the organization-level base configuration via:

  inherit_from = "github:commit-check/.github:commit-check.toml"

Only the action-repo-specific require_rebase_target is kept locally.
All other settings (commit rules, branch types, ignore_authors) are
now managed centrally in commit-check/.github/commit-check.toml.
@shenxianpeng shenxianpeng force-pushed the chore/use-inherited-org-config branch from 958d076 to 343e414 Compare June 26, 2026 21:47
@shenxianpeng shenxianpeng changed the title chore: inherit org-level config from commit-check/.github chore: switch to inherited org-level config from commit-check/.github Jun 26, 2026
@shenxianpeng shenxianpeng force-pushed the chore/use-inherited-org-config branch from 343e414 to 84ca51a Compare June 26, 2026 21:50
@shenxianpeng shenxianpeng merged commit 24ee84e into main Jun 26, 2026
10 checks passed
@shenxianpeng shenxianpeng deleted the chore/use-inherited-org-config branch June 26, 2026 21:53
@shenxianpeng shenxianpeng added chore Choses update and removed developer labels Jul 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore Choses update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant