[improve/#53] 커밋 타입 기반 적용사항-커밋 매칭 점수 보정#59
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ 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 |
✨ 작업 개요
적용사항-커밋 매칭 점수에 커밋 메시지 타입(
feat,fix,docs,chore,refactor등)을 소폭 반영해 같은 키워드를 공유하는 커밋의 추천 순위를 더 정교하게 조정했습니다.📄 작업 내용
feat(scope)!:,docs:,fix:등 conventional commit 형태 지원featfixdocs,chorerefactor+3보너스 적용chore: @ApiErrorCodeExample 적용이 Swagger 문서화 적용사항과 맞는 경우📌 관련 이슈
🔌 API 변경사항 (해당 시)
없음.
💬 기타 사항
score_breakdown구조도 유지했습니다.✅ 검증
uv run ruff check app/domains/meeting_analysis/services/matching_scoring.py tests/test_application_commit_matching_scoring.pyuv run ruff format --check app/domains/meeting_analysis/services/matching_scoring.py tests/test_application_commit_matching_scoring.pyuv run pytest tests/test_application_commit_matching_scoring.py tests/test_application_commit_matching.py