Repository navigation
perf(server): reuse origin metadata within PR lookups - #11389
yashranaway wants to merge 1 commit into
Conversation
ApprovabilityVerdict: Approved at Macroscope's review found this PR approvable — This is a small, self-contained server performance refactor that reuses origin metadata during PR lookups while preserving distinct-remote behavior. The accompanying test verifies the reduced Git configuration reads, and no production defaults, schemas, infrastructure, or sensitive areas are changed. Notes:
You can add or adjust custom eligibility rules. Learn more. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Limit details: You’ve used all 10 included reviews currently available. 📝 WalkthroughWalkthroughGitManager now shares the origin repository context when resolving pull-request identity and branch-head context. A regression test verifies that repeated warm lookups avoid GitHub calls and read the origin URL once. Suggested reviewers: ChangesGit repository context caching
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Refactor Merge Risk: ⚪ Minimal · up to The origin metadata reuse preserves repository context while avoiding duplicate configuration reads, with no current merge-blocking risk identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Usage-based review receipt
Note This review was completed with usage-based billing: files reviewed beyond your plan's included limits are billed at $0.25/file. View usage-based billing. Comment |
Dismissing prior approval to re-evaluate 221d8a2
|
Note 🤖 Claude Opus 5.5 responding on behalf of Theo Closing as superseded. The same fix landed in #16272: when a branch tracks A rebase of this branch onto |
Repeated PR lookups resolve the head remote and origin independently, even when both are
origin. This spawns two identical Git config reads during cache verification.Reuse the origin repository result within each lookup when it is also the head remote. Distinct remotes still resolve concurrently, and every request still checks current remote identity. This addresses the duplicate-read portion of #11220.
Validation: all 113 GitManager tests pass, including a regression that fails before the fix (two origin reads) and passes afterward (one). Server typecheck and targeted lint pass.
Model: GPT-6
Harness: Codex in T3 Code
Summary by CodeRabbit
Bug Fixes
Tests