docs: README quick start + auto-detection updates - #102
Conversation
`envorigin audit` / `scan` / `explain` / `graph` now work in any repo without flags: the project type is detected (compose → actions → gitlab → circleci → dotenv, the same precedence the GitHub Action wrapper uses) and the command dispatches to the right backend, with the detected file named in the output. Backend-prefixed commands stay for power users and CI pinning. Also: - positional path argument on the top-level commands: a config file or a directory to detect in (`envorigin scan ./dir`) - redaction hint: human output appends "pass --show-values to reveal" when values were hidden - friendly error when no compose/CI config is found in the target dir Tests: 9 new integration tests (auto-detection per backend, bare-dotenv directory, positional paths, empty-directory error, redaction hint). 145 total, all green; clippy -D warnings and fmt clean. Co-Authored-By: Claude <noreply@anthropic.com>
- 5-minute quick start after Install: install → cd → envorigin audit (format auto-detected), a real output sample, and a scenario table (.env mystery → explain, CI gate → audit --fail-on, team rules → init, drift → diff) - common-flags table: -f now omits to auto-detect; positional PATH documented - audit section notes top-level auto-detection; prefixed variants pin - test count 112 → 145 Co-Authored-By: Claude <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 47 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 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
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 |
CHANGELOG [1.12.0]: unified entry (auto-detection), positional path args, redaction hint. post-release-plan: UX release section marked done (pulled into 1.12.0, PR #101); docs section done (PR #102, metadata needed no change); note the CI rerun pending GitHub Actions recovery. Co-authored-by: Claude <noreply@anthropic.com>
1 participant
README onboarding fix from the product review: a 5-minute quick start right after Install (auto-detected format, real output, scenario table), updated common-flags table (-f omits to auto-detect, positional PATH), audit section notes auto-detection, test count 112 → 145.
Docs only — no code.
🤖 Generated with Claude Code