docs: make README links registry-safe - #596
seonghobae wants to merge 2 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
🚧 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. 📝 WalkthroughWalkthroughREADME의 아키텍처 문서 링크 2개를 상대 경로에서 특정 커밋의 GitHub 절대 URL로 변경했습니다. ChangesREADME 링크 업데이트
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Other 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
|
@coderabbitai review Please review exact head |
|
|
Summary
Current exact authority — 2026-09-25
main@47c6fd27de13b0da37a7db64697b869941909351305a797e336823518f3d4ae32b3d02962fcacddbREADME.mdonly; two relative architecture-document links become immutable commit-bound URLsblob/mainpackage links: 2 → 0Exact-head hosted security evidence is now terminal GREEN: Semgrep
35448033057, Security Scan35448033055, and CodeQL PR35448033010all completed successfully. Commit statuses for Devin Review and CodeRabbit are also success.The PR is not merge-authorized yet: there is still no submitted independent pull-request approval on the current exact head. Ready state only exposes the current candidate for review; it is not approval or release evidence. Predecessor-head evidence is not reused.
Canonical reusable registry/README enforcement remains owned by the dedicated
.githublane; this PR does not copy that workflow or mutate central owner state.No force push, destructive rebase, self-approval, gate weakening, scanner suppression, or source-neutral wake commit.