feat: add cwd option to staged command#16
Conversation
|
Warning Review limit reached
Next review available in: 27 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 (2)
✨ Finishing Touches🧪 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 |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9a52f35c65
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| allowEmpty: values['allow-empty'] ?? values.allowEmpty ?? false, | ||
| concurrent: values.concurrent === undefined ? true : JSON.parse(values.concurrent), | ||
| config: stagedConfig, | ||
| cwd: values.cwd, |
There was a problem hiding this comment.
cwd is only passed to lint-staged after loadRstackConfig() has already discovered rstack.config.* from the original process directory (see packages/rstack/src/config.ts:110-121). For rs staged --cwd packages/app where packages/app/rstack.config.ts defines define.staged, this still throws No define.staged config found or uses a parent config unless the user also supplies --config, even though lint-staged documents --cwd as running tasks in a specific directory. Please resolve config discovery relative to values.cwd when no explicit --config is set, or make the required --config coupling explicit.
Useful? React with 👍 / 👎.
1 participant
This PR adds
--cwd <path>support tors stagedso lint-staged can operate on a Git repository other than the CLI process directory. The option maps directly to lint-staged'scwdAPI. Integration coverage starts the CLI outside the fixture repository and verifies that tasks receive the expected relative file path from the specified cwd.