docs: assert release policy in AGENTS.md to prevent re-adding release-please - #161
Conversation
…-please Couldn't identify which session/process added release-please (PRs #156-158, merged ~19:36-19:44 UTC today) — no aoe session had a path in this repo, opencode's and omp's session DBs show no matching activity, and history:// only sees this process's own subagents. Whatever did it either ran outside any locally-tracked session or has since exited without leaving a trace I can query. Since I can't message the specific process, asserting the policy durably in the repo instead: AGENTS.md already documented 'creates release via semantic-release' in its Post-PR workflow section, but nothing said not to add a second mechanism alongside it. Now it does, explicitly, with the incident referenced by PR number.
|
Warning Review limit reached
Next review available in: 8 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. 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 |
1 participant
Couldn't identify which session/process added release-please earlier today (PRs #156-158) — no aoe session, opencode/omp session DB, or history:// registry shows matching activity for this repo at that time. Asserting the policy durably in AGENTS.md instead, since I can't message whatever did it directly: this repo releases via semantic-release only, don't add a second mechanism alongside it, with the incident referenced by PR number for context.