docs(signposts): refresh topic routing#654
Conversation
|
Warning Review limit reached
More reviews will be available in 24 minutes and 33 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: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (12)
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 |
Code Lawyer Activity Summary
Verification:
Merge-gate note: repository Actions are green, but strict Code Lawyer remains blocked by review policy / CodeRabbit status unless an admin override is explicitly accepted. |
Code Lawyer Activity Summary — Rerun
Verification:
No merge executed: the user requested admin merge only if green and clean, and the PR is not green while CodeRabbit reports |
Code Lawyer Activity Summary — Rerun 2
Verification:
No commits were created and no review threads were resolved because there were no actionable issues in this pass. |
Summary
docs/topics/docs-orientation.mdtopic for choosing the right documentation signpostwesley-cli 0.1.0and toward current0.1.1/cargo run --bin wesley -- ...docs/topicsand prevent the retired0.1.0install command from returningVerification
BATS_LIB_PATH=test/vendor bats -t test/docs-planning-boundary.batscargo xtask docs-checknode scripts/check-doc-cli-commands.mjspnpm exec prettier --check README.md CONTRIBUTING.md docs/README.md docs/GUIDE.md docs/ARCHITECTURE.md docs/ENTRYPOINTS.md docs/METHOD.md docs/reference/cli.md docs/topics/*.md docs/topics/contributing/triage.md docs/truth-manifest.jsonBATS_LIB_PATH=test/vendor bats -t test/release-governance.batsgit diff --checkcargo xtask preflight