Skip to content

feat: diff JSON output for project diffs and --fail-on-drift CI gate - #53

Merged
FIERsity merged 1 commit into
mainfrom
feat/diff-json-fail-on-drift
Aug 6, 2026
Merged

feat: diff JSON output for project diffs and --fail-on-drift CI gate#53
FIERsity merged 1 commit into
mainfrom
feat/diff-json-fail-on-drift

Conversation

@FIERsity

@FIERsity FIERsity commented Aug 6, 2026

Copy link
Copy Markdown
Owner

What

  • diff --project-a/--project-b now honors --format json — machine-readable drift reports with sensitive values redacted unless --show-values
  • New --fail-on-drift flag on both diff modes: exits 1 when any variable carries different values, turning drift detection into a CI gate

Why

Project diff only had human output; CI consumers had no machine-readable format and no exit code to fail on. This closes the gap with the same conventions as audit (--format json, fail-to-exit semantics).

Verification

  • 5 new integration tests (diff JSON redaction, fail-on-drift failure/success for both files and project modes)
  • cargo test 116 green, clippy clean, fmt clean

- diff --project-a/--project-b now honors --format json (sensitive values
  redacted unless --show-values)
- new --fail-on-drift flag on both diff modes exits 1 when a variable
  carries different values, making drift detection usable as a CI gate
- 5 new integration tests (116 total green)
@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 40 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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: cbc55cc2-4023-4e2f-b778-e53f9c35ad98

📥 Commits

Reviewing files that changed from the base of the PR and between 20478a2 and 037347d.

📒 Files selected for processing (6)
  • CHANGELOG.md
  • README.md
  • src/cli.rs
  • src/diff.rs
  • src/main.rs
  • tests/cli.rs

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.

@FIERsity
FIERsity merged commit 9ac526f into main Aug 6, 2026
2 checks passed
@FIERsity
FIERsity deleted the feat/diff-json-fail-on-drift branch August 6, 2026 01:41
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.

1 participant