Skip to content

feat(logging): add configurable warning level - #211

Merged
mike1858 merged 1 commit into
Piebald-AI:mainfrom
jimyag:feat/configurable-log-level
Jul 22, 2026
Merged

feat(logging): add configurable warning level#211
mike1858 merged 1 commit into
Piebald-AI:mainfrom
jimyag:feat/configurable-log-level

Conversation

@jimyag

@jimyag jimyag commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add a persistent [logging] configuration with warn and error levels
  • support splitrail config set log-level <warn|error> and expose the active level in config show
  • suppress warn_once output at the error level while preserving existing warning content and error output
  • document the new configuration and cover defaults, updates, and invalid values

Behavior

The default level remains warn, so existing configurations and per-session warning details are unchanged. Users who only want errors can run:

splitrail config set log-level error

Validation

  • cargo build --quiet
  • cargo test --quiet (393 passed)
  • cargo clippy --quiet -- -D warnings
  • cargo doc --quiet
  • cargo fmt --all --quiet

Allow users to persist warn or error logging levels without CLI flags. Collapse repeated Codex fallback warnings into a single startup message.

Signed-off-by: jimyag <git@jimyag.com>
@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jimyag, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 39 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 4da8a974-2779-4f1d-9ede-74dadfbd0386

📥 Commits

Reviewing files that changed from the base of the PR and between 658a746 and 921236a.

📒 Files selected for processing (5)
  • README.md
  • src/analyzers/codex_cli.rs
  • src/config.rs
  • src/main.rs
  • src/utils.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Comment @coderabbitai help to get the list of available commands.

@mike1858
mike1858 enabled auto-merge (squash) July 22, 2026 16:04
@mike1858
mike1858 merged commit 7eb4b07 into Piebald-AI:main Jul 22, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants