fix(setup): validate Git hooks directory - #104
Conversation
|
Warning Review limit reached
Next review available in: 38 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)
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 |
Deploying rstack-cli with
|
| Latest commit: |
9140b03
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5a2063f6.rstack-cli.pages.dev |
| Branch Preview URL: | https://chenjiahan-fix-setup-hooks-d.rstack-cli.pages.dev |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9140b03361
ℹ️ 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".
| return fail('invalid-hooks-directory', 'Git hooks directory must not be empty.'); | ||
| } | ||
|
|
||
| if (path.isAbsolute(resolvedDir)) { |
There was a problem hiding this comment.
Reject drive-qualified Windows hook paths
On Windows, a drive-relative input such as --hooks-dir C:hooks is not considered absolute by path.isAbsolute, so it passes this validation even though it is not relative to cwd. The later path.join(cwd, resolvedDir, '_') produces a path containing C: as an interior component, causing setup to fail with a filesystem write-failed error instead of the intended invalid-directory diagnostic; reject paths with a drive root as well.
Useful? React with 👍 / 👎.
Invalid
--hooks-dirvalues can produce unintended or mismatched Git hook targets. This PR normalizes hook directory separators and rejects empty or absolute paths before touching Git or the filesystem. It also covers the CLI exit status and diagnostics for both cases.