docs: rework the README to the org layout and fix outdated facts - #289
shenxianpeng wants to merge 1 commit into
Conversation
Follow the layout the other cpp-linter READMEs move to: name, four badges, one sentence, a link line, then Quick start, Usage, topic sections, Used by, Contributing and License. Fix what no longer matches the code: the hooks install the newest wheel on every run instead of a bundled default, the mirrors-clang-format comparison, and the --export-fixes warning. Use full URLs so the PyPI page links work, and drop the duplicated sections. In examples/, drop --checks=.clang-tidy (a check glob, not a file), the unsupported "~80%" claim and rev v1.5.0.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #289 +/- ##
=======================================
Coverage 97.53% 97.53%
=======================================
Files 3 3
Lines 243 243
=======================================
Hits 237 237
Misses 6 6 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Caution Review failedFailed to post review comments. GitHub was unavailable or timed out while CodeRabbit was posting the review. Please request a new review later if the pull request still needs one. This happened while posting 2 inline comments. Use ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (4)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. ⏰ Context from checks skipped due to timeout. (20)
WalkthroughThe README was reorganized to cover setup, clang tool usage, compilation databases, pre-commit behavior, and feature comparisons. The example guides update hook settings, CI action versions, and clang-format dry-run descriptions. ChangesDocumentation and examples
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 2 systems. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 |



Part of aligning the READMEs across the org. Every README gets the same opening (name, badges, one sentence, a link line) and the same section order: Quick start, Usage, topic sections, Used by, Contributing, License.
What changed
Header
Wrong or outdated, now fixed
--versioninstalls the newest wheel on PyPI at every run.--style,--verboseor dry-run. It has all three (tested), so the ✅/❌ table becomes plain text.--export-fixeswarning blamed--jobs, but the hook already turns--jobsoff for that flag. The real collision is pre-commit running groups of files in parallel: with 12 files,fixes.yamlkept 4 entries, and 12 withrequire_serial: true.Removed
<p align>HTML in Used by. Each org is now its avatar and name in one link.examples/
--checks=.clang-tidyremoved: it is a check glob, not a file, and clang-tidy finds.clang-tidyby itself.rev: v1.5.0becomesv1.6.0,checkout@v4/setup-python@v5become v7, and the "~80%" claim is gone.Checked
rev: v1.6.0in scratch repos.compile_commands.json.readme_rendererrenders the README without warnings, so the PyPI page will render.Note
--dry-runkeeps a v1.6.0 caveat, because in v1.6.0 it always passes. Releasing v1.6.1 (draft) removes the need for it.revwould then move to v1.6.1 here and on the website.Summary by CodeRabbit