chore: add monthly full rag evaluation workflow - #133
Conversation
|
Warning Review limit reached
More reviews will be available in 49 minutes and 33 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthrough월간 스케줄(UTC 매월 20일 14:00) 및 수동 트리거로 RAG 전체 평가를 수행하는 GitHub Actions 워크플로우( ChangesRAG Full Evaluation CI 워크플로우 추가
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/rag-full-evaluation.yml:
- Line 23: The GitHub Actions workflow uses floating version tags for
actions/checkout and actions/upload-artifact which poses supply chain security
risk. Replace the floating version tags (actions/checkout@v5 on line 23 and
actions/upload-artifact@v4 on line 128) with their corresponding 40-character
commit SHAs to pin to exact versions and eliminate the supply chain
vulnerability.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 3a8ed3cf-49f6-434f-a337-48eacb5ae146
📒 Files selected for processing (3)
.github/workflows/rag-full-evaluation.yml.gitignoreREADME.md
🎯 배경
🔍 주요 내용
RAG Full EvaluationGitHub Actions workflow를 추가했습니다.scripts/check_rag_eval.sh를 재사용해 full RAG report를 생성합니다..gitignore에서tests/reports/**/*.json은 계속 ignore하되,tests/reports/chatbot/*-rag_eval_summary.json은 공개 가능한 요약 리포트로 추적 가능하게 예외 처리했습니다.tests/reports/chatbot/rag_eval_report.json기준으로 정리했습니다.변경 요약
매월 20일 23:00 KST에 자동 실행되는 RAG 전체 평가 워크플로우를 추가했습니다. 상세 평가 결과는 로컬에만 보관하고, 요약 리포트만 GitHub Artifacts에 공개하는 방식으로 구현했습니다.
주요 변경점
errors필드 등)를 제거한 sanitized 요약 생성*-rag_eval_summary.json파일은 추적 가능하도록 명시적 제외주의/리스크
다음 액션