ci: PR 커밋 메시지 commitlint 검사 추가#12
Conversation
|
Warning Review limit reached
Next review available in: 25 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
PR의 모든 커밋 메시지를 conventional commits 규칙으로 검사한다. rebase 머지가 개별 커밋을 그대로 main에 올리므로 커밋별 위생을 CI에서 강제.
commitlint.config.mjs: pilot과 동일 규칙(한글 subject·72/50자·type-enum). rutter는 node 프로젝트가 아니라 config 파일만 둔다wagoid/commitlint-github-action@v6가 base..head 전체 커밋을 검사.gitignore화이트리스트에.github/·commitlint.config.mjs추가 (CI 파일 관리 대상 편입)commitlint체크를 required로 지정 예정🤖 Generated with Claude Code