fix: add zizmor config flag to pre-commit hook for CI parity#4
Conversation
|
Warning Rate limit exceeded
⌛ 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)
📝 Coding Plan
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.
Pull request overview
This PR aims to ensure the local zizmor pre-commit hook runs with the same configuration as the repository’s CI zizmor job, reducing mismatched findings between developer machines and CI.
Changes:
- Update the
zizmorpre-commit hook command to pass an explicit config file (--config zizmor.yml).
You can also share your feedback on Copilot code review. Take the survey.
| - id: zizmor | ||
| name: zizmor | ||
| entry: zizmor .github/workflows/ | ||
| entry: zizmor --config zizmor.yml .github/workflows/ |
Summary
--config zizmor.ymlto the zizmor pre-commit hook entry so local and CI results matchTest plan