[Demo] Link the performance tuning guide from the introduction - #13
[Demo] Link the performance tuning guide from the introduction#13HardMax71 wants to merge 1 commit into
Conversation
|
Warning Review limit reached
Next review available in: 17 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
HardMax71
changed the title
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 1 file
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="docs/src/introduction.md">
<violation number="1" location="docs/src/introduction.md:48">
P1: The self-scan will report this new Markdown reference as an explicit-target-missing finding because `tuning.md` is absent, causing `enforce` to block the merge. Removing this paragraph until the guide is added, or adding the target in this PR, keeps the scan green.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| - Every internal limit is a published number. Hitting one produces a typed error naming the | ||
| limit and the observed value, never a hang or a silent cutoff. | ||
|
|
||
| For squeezing the last milliseconds out of large repositories, see the |
There was a problem hiding this comment.
P1: The self-scan will report this new Markdown reference as an explicit-target-missing finding because tuning.md is absent, causing enforce to block the merge. Removing this paragraph until the guide is added, or adding the target in this PR, keeps the scan green.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/src/introduction.md, line 48:
<comment>The self-scan will report this new Markdown reference as an explicit-target-missing finding because `tuning.md` is absent, causing `enforce` to block the merge. Removing this paragraph until the guide is added, or adding the target in this PR, keeps the scan green.</comment>
<file context>
@@ -44,3 +44,6 @@ Each promise below is enforced by a test in the suite:
- Every internal limit is a published number. Hitting one produces a typed error naming the
limit and the observed value, never a hang or a silent cutoff.
+
+For squeezing the last milliseconds out of large repositories, see the
+[performance tuning guide](tuning.md).
</file context>
The guide itself is coming in a follow-up, definitely.
The guide is coming in a follow-up, definitely. Nothing to see here.
(A demonstration: this PR links a page that does not exist, and the repository's own scanner reviews every pull request under enforce. It should refuse this one with an introduced explicit-target-missing finding and block the merge. Do not merge; close after admiring the red X.)
Summary by cubic
Add a link to the performance tuning guide from the Introduction page to improve discoverability. The link points to
tuning.mdfor tips on speeding up large repositories and will be added in a follow-up.Written for commit 4d800c5. Summary will update on new commits.