Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
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. ✨ 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 |
요약
pre-commit/pre-push를 GitHub CI의 변경 감지 기준(apps/web,apps/admin, 루트 핵심 파일)과 동일하게 정렬했습니다.docs/development-workflow.md에 새 훅 동작(검사/빌드 범위 및 실행 명령)을 반영했습니다.CI 실패 원인 (기존)
해결 방식
pre-commit: staged 파일 기준으로 대상 판별 후pnpm --filter @solid-connect/web run ci:checkpnpm --filter @solid-connect/admin run lint+pnpm --filter @solid-connect/admin run formatpre-push: upstream(or merge-base) 대비 변경 파일 기준으로 대상 판별 후NODE_ENV=production pnpm --filter @solid-connect/web run buildNODE_ENV=production pnpm --filter @solid-connect/admin run build검증
sh .husky/pre-commitsh .husky/pre-pushpnpm --filter @solid-connect/admin run test(현재 테스트 파일 부재로No test files found확인)리스크/참고