| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Add the v2.13.1 entry covering the checked-value reporting in JSON output (#522) and the commit-check.com link in the config header (#524), plus the Highlights row.
✅ Deploy Preview for commit-check ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Sorry, something went wrong.
|
Warning Review limit reached@shenxianpeng, you've reached your PR review limit, so we couldn't start this review. Next review available in: 56 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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR. 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 1a5b4f28-0a72-407c-b11f-c0ccc5258371 📥 CommitsReviewing files that changed from the base of the PR and between 219eaa4 and bfee058. 📒 Files selected for processing (1)
WalkthroughThe changelog adds a v2.13.1 highlight and release section. It documents validated values in passing JSON output and validate_all_detailed(), unchanged terminal output, and the commit-check.com link in generated cchk.toml files. Changesv2.13.1 release documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
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. ❤️ ShareComment @coderabbitai help to get the list of available commands. |
Sorry, something went wrong.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agentsVerify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. Inline comments: In `@docs/changelog.md`: - Line 14: Update the changelog link in the 2.13.1 entry to reference the actual heading fragment in docs/example.md, or add a stable explicit anchor there and link to it. Preserve the existing destination section and link text.
Fix all unresolved CodeRabbit comments on this PR:
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 516fe3a4-3668-4c77-a8e2-b8cfa6d14245
📥 CommitsReviewing files that changed from the base of the PR and between b6ea850 and 219eaa4.
📒 Files selected for processing (1)
Sorry, something went wrong.
|
|
||
| | Version | What changed | Documented in | | ||
| |---|---|---| | ||
| | [2.13.1](#v2131) | JSON output reports the checked value for passing checks | [Output for scripts and CI](example.md#output-for-scripts-and-ci) | |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Fix the broken recipe link.
markdownlint-cli2 reports that #output-for-scripts-and-ci is not a valid fragment in docs/example.md. Update the fragment to the actual heading anchor or add a stable explicit anchor.
🧰 Tools 🪛 markdownlint-cli2 (0.23.2)[warning] 14-14: Link fragments should be valid
(MD051, link-fragments)
🤖 Prompt for AI AgentsVerify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/changelog.md` at line 14, Update the changelog link in the 2.13.1 entry to reference the actual heading fragment in docs/example.md, or add a stable explicit anchor there and link to it. Preserve the existing destination section and link text.
Source: Linters/SAST tools
Sorry, something went wrong.
A comment link in the generated cchk.toml template does not change user-visible behavior and is below the changelog's bar for notable changes.
| Back | FazBrowse Home | New Git URL |
What
Adds the v2.13.1 entry to the changelog: