ci: drop housekeeping reviewer-request for native team assignment - #311
Conversation
The wavehouse-admins team now has repo access and code-review assignment (load-balanced) configured, so GitHub handles reviewer routing natively: the required_reviewers ruleset rule requests the team on every PR and the team auto-assigns + load-balances a member. That makes housekeeping's manual reviewer pick/request redundant. - housekeeping.yml: remove the pick-reviewer + assign-and-request-review steps (and the board-config load); it now only labels + lints the title. - Delete the now-unused .github/actions/assign-and-request-review composite. - board-config.env: drop ADMINS (its last consumer gone) — kills the team-vs-ADMINS drift; the file now only carries Task Board IDs. - Doc-sync: AGENTS.md (review-tooling table, reviewer-assignment rule, governance files), development.md, claude-code.md. Side benefit: removing the board-config-load step also clears the pre-existing SC2086 actionlint warning on that line. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 37 minutes and 14 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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 |
|
📚 Docs preview is live → https://ee427e07-wavehouse-docs.wave-rf.workers.dev
|
Summary
Now that the
wavehouse-adminsteam has repo access and code-review assignment (load-balanced) configured, reviewer routing is fully GitHub-native — so this removes the now-redundanthousekeeping.ymlreviewer machinery.The native flow: the
required_reviewersruleset rule requests the@Wave-RF/wavehouse-adminsteam on every PR → the team's code-review assignment auto-assigns + load-balances a specific member → their approval satisfies the rule.Changes
housekeeping.yml— remove thepick-reviewerstep, theAssign + request reviewstep (which used the composite), and theLoad board configstep. It now does only: path-labeling + PR-title-lint + the title-fail sticky comment..github/actions/assign-and-request-review/— the composite's only remaining consumer (afterdependabot-automerge.ymlwas removed in ci: replace admin-approval workflow with native required_reviewers #310).board-config.env— dropADMINS(its last consumer gone), killing the team-membership-vs-ADMINSdrift; the file now carries only Task Board IDs fortriage.yml.AGENTS.md,docs/src/content/docs/development.md,docs/src/content/docs/claude-code.md,CHANGELOG.md.Net
−229 lines. Bonus: removing the board-config-load step also clears a pre-existing
SC2086actionlint warning on that line.Testing
make cigreen; both pre-push reviewers (pre-push-reviewer,docs-reviewer) →ship_it. The native reviewer-assignment behavior validates on the next non-bypass PR (this PR still triggersmain's housekeeping viapull_request_targetuntil merged).🤖 Generated with Claude Code