chore(hooks): scope readme_guard to repo tree only#137
Conversation
The hook was blocking writes to paths outside the fbuild repo (e.g. ~/.claude/projects/.../memory/) because it checked every directory on disk. Now early-returns when the file_path resolves outside the cwd's repo root. Writes inside the repo still enforce the README rule. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 21 minutes and 52 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
Summary
ci/hooks/readme_guard.pywas blockingWriteoperations anywhere on disk, including outside the fbuild repo. That came up while writing to Claude's user-level memory directory (~/.claude/projects/.../memory/) — the hook demanded aREADME.mdin a directory the repo doesn't own.Change
Early-return when the written file resolves outside the repo root (the hook runs with
cwd = git rev-parse --show-toplevel, soPath.cwd().resolve()is the repo root at invocation time).Verified:
Test plan
🤖 Generated with Claude Code