feat(template): scaffold Claude Tier 0 baseline review caller in generated repos#100
feat(template): scaffold Claude Tier 0 baseline review caller in generated repos#100williaby wants to merge 1 commit into
Conversation
…rated repos
Generated projects now ship .github/workflows/claude-baseline-review.yml, a thin caller of the org reusable baseline reviewer in ByronWilliamsCPA/.github, so new repos inherit the Tier 0 reviewer at scaffold time. repo-description is templated from project_short_description; the ANTHROPIC_API_KEY ${{ ... }} reference is wrapped in a Jinja {% raw %} guard so it survives rendering; no caller-level concurrency block (the reusable owns concurrency). Pin matches the fleet rollout (8de6560). Part of the org-wide tiered-pr-review rollout.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 38 minutes and 29 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?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 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Summary
Generated projects now ship
.github/workflows/claude-baseline-review.yml, so every newly-scaffolded repo inherits the Tier 0 Claude baseline PR reviewer at creation time, with no manual per-repo step. This complements the org-wide rollout that added the caller to the ~21 existing repos.The generated file is a thin caller of the org reusable in
ByronWilliamsCPA/.github, matching the hardened pattern proven across the fleet:.githubmain SHA (8de6560), the same pin used in the fleet rollout; Renovate-tracked in generated repos.repo-descriptionis templated from{{ cookiecutter.project_short_description }}so each generated repo gets accurate framing.ANTHROPIC_API_KEY${{ ... }}reference is wrapped in a Jinja{% raw %}{% endraw %}guard (the repo's standard convention, seesonarcloud.yml) so the GitHub Actions expression survives template rendering.secrets: inherit.concurrencyblock (the reusable owns concurrency; a caller block would deadlock the run at startup).Verification
cookiecutter . --no-input; the rendered caller is valid (the${{ ... }}andpermissions: {}render correctly) and passesactionlint.pre-commit runon both changed files passes (detect-secrets honors the# pragma: allowlist secret, no-em-dash, markdownlint, codespell, TruffleHog).test_github_workflows_generatedand the baked-YAML validity loop intest_zero_issues.pypass. The 8 failing tests in that suite are pre-existingModuleNotFoundError: No module named 'tomli'env gaps (confirmed identical with this change stashed), unrelated to a workflow-YAML + CHANGELOG change.The
ANTHROPIC_API_KEYorg secret (visibility: all) and the org-wide Claude GitHub App mean generated repos under the org need no additional setup.