docs: Add Used By section to README#229
Conversation
|
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #229 +/- ##
=======================================
Coverage 97.07% 97.07%
=======================================
Files 4 4
Lines 239 239
=======================================
Hits 232 232
Misses 7 7 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|



Summary
Adds a
Used Bysection to the README using the same compact avatar-and-name style ascpp-linter-action.The section highlights a few public users of
cpp-linter-hooksand linksmany moreto GitHub code search results, so maintainers do not need to curate every usage request through PRs.Validation
uvx prek run --files README.mdNote:
./.venv/bin/pre-commit run --files README.mdfailed because the local pre-commit version does not accept the current hook manifeststages: pre-commitvalue.