chore: strip residual label-convention rules (followup)#18
Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
Followup to the org-wide label-convention strip merged earlier today. The upstream
Open-Paws/structured-coding-with-ai#49deleted these files in the canonical source, but they did not auto-propagate to this repo (sync mechanism either doesn't run on this repo or only propagates additions, not deletions).Changes
Delete
.claude/rules/:pipeline-nevers.md(encodes label-driven gate semantics)parallelization.md(encodes label-driven wave dispatch)desloppify.md(label-prescribing variant)Why
Layer-3 dispatcher is stopped. All label definitions across the org have already been deleted. Leaving these rules files in place keeps stale label-name references in the rules tree.
🤖 Generated with Claude Code