test(staged): cover rs fmt integration - #127
Conversation
|
Warning Review limit reached
Next review available in: 53 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdded staged-format CLI integration tests. The tests create isolated temporary Git projects and invoke 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@packages/rstack/tests/cli/staged/fmt.test.ts`:
- Around line 42-48: Update the test environment setup around the env object to
remove inherited GIT_* variables, especially GIT_DIR, GIT_WORK_TREE, and
GIT_INDEX_FILE, before assigning the fixture-specific GIT_CONFIG_GLOBAL and
GIT_CONFIG_NOSYSTEM values. Preserve the existing process environment and color
settings while ensuring Git operates on projectPath.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: e35a4abc-91ac-4518-8ba4-af746a8ff638
📒 Files selected for processing (1)
packages/rstack/tests/cli/staged/fmt.test.ts
Deploying rstack-cli with
|
| Latest commit: |
48ef6e2
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c9692af0.rstack-cli.pages.dev |
| Branch Preview URL: | https://chenjiahan-test-staged-fmt-i.rstack-cli.pages.dev |
This PR adds an end-to-end Git fixture for passing staged files from
rs stagedtors fmt. It covers filenames with spaces, explicit staged files ignored by.gitignore,define.fmt.ignorePatterns, Git index updates, and formatter failure propagation.