Conversation
Run `go test -race` on every PR + push to main. Closes the -race-in-CI gap from the 9-repo bug-class scan (epic ccp-sbp, decision d7ea466a8172). Review-only — do not merge without a maintainer pass.
|
Warning Review limit reached
Next review available in: 57 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 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe pull request adds a GitHub Actions workflow that runs Go validation for pull requests and pushes to ChangesGo CI workflow
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/check.yml:
- Line 20: Update the actions/checkout@v4 step in the workflow to disable
credential persistence by setting persist-credentials to false, ensuring
subsequent pull-request-controlled Go test steps cannot access the workflow
token.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: fda5d211-945b-4b13-8880-ef6c8d37bebf
📒 Files selected for processing (1)
.github/workflows/check.yml
|
Applied CodeRabbit's one actionable finding: added |
What
Adds a
checkCI workflow runninggo test -race -count=1 ./...on every PR and push to main.Why
The 9-repo bug-class scan (2026-08-04, decision nug
d7ea466a8172, epicccp-sbp.4) found concurrency-lifecycle defects as a recurring, race-detector-catchable class. This repo had no CI test gate — race ran only in localmake audit. This closes the gap.Notes
-racegap only (goleak/synctest wiring is per-repo judgment, documented separately).-race.Summary by CodeRabbit