feat: add logs about summarizing PR reviews

[2bndy5]

resolves #341

Summary by CodeRabbit

• Refactor

  • Reorganized status message handling to emit information through logging instead of including it in markdown output
  • Improved duplicate concern tracking with enhanced logging for removal processes
  • Added diagnostic logging when no concerns are detected

• Tests

  • Enhanced test documentation and logging initialization configuration

[coderabbitai]

Warning

Review limit reached

@2bndy5, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 50 minutes and 23 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 9fc6d070-443b-418d-bff1-49550f1a6620

📥 Commits

Reviewing files that changed from the base of the PR and between f6f6c4f and 07c5617.

📒 Files selected for processing (1)

• cpp-linter/src/clang_tools/mod.rs

📝 Walkthrough

Walkthrough

ReviewComments::summarize is updated so three informational strings (diff-fit count, duplicate removal, and LGTM) are emitted via log::info! instead of being appended to the returned markdown body. The summarize_reused_reviews unit test gains doc comments and a conditional logger initialization block under the bin feature.

Changes

Summarize logging and test update

Layer / File(s)	Summary
Move summarize messages to log::info! cpp-linter/src/clang_tools/mod.rs	In ReviewComments::summarize, the "concerns fit within diff" line moves from the markdown body to log::info!; duplicate removal extracts a dupes variable and adds log::info!; the no-concerns/no-full-patch path adds log::info!("No concerns to report: LGTM").
Test doc comments and conditional logger init cpp-linter/src/clang_tools/mod.rs	summarize_reused_reviews receives explanatory doc comments and a #[cfg(feature = "bin")] block that calls crate::logger::try_init() and sets the max log level to Info.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• cpp-linter/cpp-linter-rs#101: Directly modifies the same ReviewComments::summarize control-flow branches in cpp-linter/src/clang_tools/mod.rs, including tool_total and indexing logic.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The pull request partially addresses issue #341 by adding logging for reused reviews and a success message, but does not fully implement logging about skipped new reviews or improve PR review summary comment wording as requested.	Complete the implementation by adding logs when reviews are reused and skipped, and update PR review summary comment wording to better communicate reuse scenarios as specified in issue #341.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change—adding logging functionality for PR review summarization—which aligns with the primary objective of the pull request.
Out of Scope Changes check	✅ Passed	All changes are directly related to logging and review summarization functionality. Test updates and logging additions align with the PR's stated objective to add logs about summarizing PR reviews.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.42%. Comparing base (619e877) to head (07c5617).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #371   +/-   ##
=======================================
  Coverage   92.42%   92.42%           
=======================================
  Files          23       23           
  Lines        3631     3632    +1     
=======================================
+ Hits         3356     3357    +1     
  Misses        275      275           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.