ci(coderabbit): make Docstring Coverage advisory#105
Conversation
This repository holds no docstring-bearing production code — it is declarative org configuration, workflow templates, docs and one bash test script. CodeRabbit's Docstring Coverage pre-merge check therefore reports 0.00% against an 80% threshold and blocks merges on a documentation gap that does not exist. It is currently the only failed pre-merge check on #103, whose changeset is YAML manifests, a bash test and Markdown. The metric cannot be scoped per-path (path_filters would drop the files from the whole review, not just this check), so make it advisory instead of a merge error. CodeRabbit still reports the coverage. inheritance: true keeps every org/UI setting intact so this stays scoped to the one value. Mirrors devantler-tech/ksail#6145. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai review |
|
✅ Action performedReview finished.
|
|
Warning Review limit reached
Next review available in: 9 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. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
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 |
@coderabbitai review |
|
✅ Action performedReview finished.
|
@coderabbitai review |
|
✅ Action performedReview finished.
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 29a4f7ad15
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
@coderabbitai review |
|
✅ Action performedReview finished.
|
@codex review |
|
Codex Review: Didn't find any major issues. Can't wait for the next one! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
1 participant
Why
CodeRabbit's Docstring Coverage pre-merge check reports 0.00% on this repository and blocks merges against an 80% threshold — but there is nothing here for it to measure. This repo holds no Go (or any other docstring-bearing) production code: it is declarative org configuration, workflow templates, docs, and one bash test script.
It is currently the only failed pre-merge check on #103, whose changeset is YAML manifests, a bash test and Markdown. You've said you won't promote drafts whose pre-merge checks aren't green, so this metric is gating real work while measuring a documentation gap that doesn't exist.
What
Adds a
.coderabbit.yamlmaking that one check advisory instead of a merge error. CodeRabbit still reports the coverage — it just no longer blocks.inheritance: truekeeps every org/UI setting intact, so this is scoped to the single value.Same fix, same reason, as devantler-tech/ksail#6145. The check can't be scoped per-path, which is why the mode is the only lever.
Unblocks #103.