Skip to content

[improve/#53] 커밋 타입 기반 적용사항-커밋 매칭 점수 보정#59

Merged
wantkdd merged 5 commits into
developfrom
improve/wantkdd-commit-type-score#53
May 14, 2026
Merged

[improve/#53] 커밋 타입 기반 적용사항-커밋 매칭 점수 보정#59
wantkdd merged 5 commits into
developfrom
improve/wantkdd-commit-type-score#53

Conversation

@wantkdd
Copy link
Copy Markdown
Collaborator

@wantkdd wantkdd commented May 14, 2026

✨ 작업 개요

적용사항-커밋 매칭 점수에 커밋 메시지 타입(feat, fix, docs, chore, refactor 등)을 소폭 반영해 같은 키워드를 공유하는 커밋의 추천 순위를 더 정교하게 조정했습니다.

📄 작업 내용

  • 커밋 메시지 prefix에서 commit type 추출
    • feat(scope)!:, docs:, fix: 등 conventional commit 형태 지원
  • 적용사항 문맥에서 기대 commit type 추론
    • 구현/추가/도입/연동 → feat
    • 오류/버그/예외/문제 → fix
    • Swagger/OpenAPI/문서/명세 → docs, chore
    • 리팩토링 → refactor
  • commit type이 적용사항 성격과 일치하면 +3 보너스 적용
  • 타입이 불일치해도 감점하지 않도록 처리
    • 추론 오류로 정답 커밋이 밀리는 상황 방지
  • goal mismatch 판정은 타입 보너스로 구제하지 않도록 기존 안전장치 유지
  • 타입이 맞는 추상 커밋 메시지는 추상 커밋 페널티를 면제
    • 예: chore: @ApiErrorCodeExample 적용이 Swagger 문서화 적용사항과 맞는 경우

📌 관련 이슈

🔌 API 변경사항 (해당 시)

없음.

💬 기타 사항

  • 응답 DTO 필드는 변경하지 않았습니다.
  • score_breakdown 구조도 유지했습니다.
  • 타입 보정은 필터가 아니라 작은 가산점이라 관련 커밋 누락 위험을 줄이는 방향입니다.

✅ 검증

  • uv run ruff check app/domains/meeting_analysis/services/matching_scoring.py tests/test_application_commit_matching_scoring.py
  • uv run ruff format --check app/domains/meeting_analysis/services/matching_scoring.py tests/test_application_commit_matching_scoring.py
  • uv run pytest tests/test_application_commit_matching_scoring.py tests/test_application_commit_matching.py

@wantkdd wantkdd added the 🚀 Feat 기능 구현 및 수정 label May 14, 2026
@wantkdd wantkdd self-assigned this May 14, 2026
@wantkdd wantkdd requested a review from Yujin1219 May 14, 2026 08:51
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 14, 2026

Warning

Rate limit exceeded

@wantkdd has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 24 minutes and 52 seconds before requesting another review.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: c390432a-ff4b-41f8-a14e-ed155b9b58ae

📥 Commits

Reviewing files that changed from the base of the PR and between 1102909 and cec1cb4.

📒 Files selected for processing (5)
  • app/domains/commit/schemas.py
  • app/domains/commit/services/matching.py
  • app/domains/meeting_analysis/services/matching_scoring.py
  • tests/test_application_commit_matching.py
  • tests/test_application_commit_matching_scoring.py
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch improve/wantkdd-commit-type-score#53

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@wantkdd wantkdd merged commit a7e61a5 into develop May 14, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🚀 Feat 기능 구현 및 수정

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[improve] 커밋 타입 기반 적용사항-커밋 매칭 점수 보정

1 participant