ci: add semantic-data-portal hourly review-repair caller - #1343
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughSemantic Data Portal에 매시 59분 실행되는 리뷰 수정 호출자를 추가했다. 호출자는 중앙 스케줄러에 작업을 위임하고, 정확한 HEAD, 권한, 시크릿 및 재시도 정책을 적용한다. 운영 문서와 계약 테스트도 추가했다. ChangesSemantic Data Portal 리뷰 수정
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to The PR adds the hourly caller and its stated minute-31 schedule; no actionable merge-blocking risk remains beyond normal review of the documented scheduling rationale. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 6 functions across 1 files. (2 skipped: 2 unsupported.) ✨ 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 |
e291c81 to
ca94993
Compare
Adds the protected hourly caller at minute 31 (free slot across all other product callers), delegating to the central pr-review-fix-scheduler with the standard one-dispatch budget and two-hour same-head retry floor. Ships the doctoring record (RCA/feasibility, cadence, credential boundary, authority boundaries incl. Keyverse/GRC/naruon/LineageWeave) and caller contract tests mirroring the disksage pattern. Closes ContextualWisdomLab/semantic-data-portal#77's hourly-trigger requirement without touching COPILOT_GITHUB_TOKEN or review-agent key contracts.
a5841c5 to
4189e6a
Compare
Summary
ContextualWisdomLab/semantic-data-portalat minute 31 — a free slot across every existing product caller (2, 10, 14, 16, 21, 23, 27, 37, 43, 49, 53, 58) and clear of the minute-zero surge.pr-review-fix-scheduler.yml: max 50 PRs inspected, one bounded dispatch, two-hour same-head retry floor, non-cancelling single-flight.docs/doctoring/semantic-data-portal-hourly-review-caller.md(RCA + remediation feasibility rationale, cadence/concurrency, credential boundary, authority boundaries: Keyverse identity, GRC policy truth, naruon document-KG writes, LineageWeave lineage reconstruction).NVIDIA_NIM_API_KEY, noCOPILOT_GITHUB_TOKEN, nosecrets: inherit.Fulfills the hourly-trigger requirement of semantic-data-portal#77 (Autonomous Data Management Commercial Loop) using the established central scheduler; review-agent credential contracts untouched.
Validation
uv run --with pytest python -m pytest tests/test_semantic_data_portal_hourly_review_caller.py→ 4 passed.Summary by CodeRabbit
새 기능
문서
테스트