[FIX] 프로젝트 상세 팀원 이름 조회 활동 상태 필터 추가#602
Conversation
|
Warning Review limit reached
Next review available in: 32 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: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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 |
Test Results418 tests 418 ✅ 12s ⏱️ Results for commit fca6ca0. |
📊테스트 커버리지
|
#️⃣연관된 이슈
close #601
📝 작업 내용
ACTIVE,COMPLETED인 경우만 직군별 팀원 이름에 포함WITHDRAWN상태 일반 구성원이 팀원 이름 조회에서 제외되는 테스트 보강🙏 리뷰 요구사항 (선택)
[fix],[test]커밋으로 분리했습니다.검증 내용:
./gradlew test --tests org.ject.support.domain.member.repository.MemberActivityRepositoryTest -x jacocoTestCoverageVerification