Repository navigation
fix(web): keep grouped project icons consistent in settings - #14493
hpflatorre wants to merge 1 commit into
Conversation
ApprovabilityVerdict: Approved at Macroscope's review found this PR approvable — This is a focused settings bug fix that aligns grouped project icons, titles, and picker defaults with the sidebar representative while preserving existing update and file-browsing behavior. It adds targeted regression coverage without introducing new capabilities, schema changes, or production infrastructure changes. Notes:
You can add or adjust custom eligibility rules. Learn more. |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: pingdotgg/t3code/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughGrouped project settings now use the member identified by the selected group as their representative and retain the full member list. The settings panel reads icon and favicon values from the group and uses a separate member for favicon picker paths. ChangesGrouped Project Settings
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix · Severity of issue fixed: Low Merge Risk: ⚪ Minimal · up to Settings previews now follow the sidebar representative or the selected checkout when filtered, while file browsing keeps its existing checkout selection. No actionable merge-blocking risk is identified. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Dismissing prior approval to re-evaluate 5177979
Problem
With connected checkouts of the same repository, Project settings can show a custom icon in the project selector but an automatic monogram in the icon preview. This occurs when a remote checkout is registered before the primary checkout: the selector uses the sidebar representative, while the preview uses the first checkout with server configuration.
Change
Use the sidebar representative for the icon preview, description, and picker defaults. When an environment or checkout filter excludes that representative, use the selected checkout's complete identity. Keep favicon file browsing on an available checkout.
Scope and approval
Closes #11835. This follows the maintainer's preview-only triage. Saved-icon synchronization and edit/reset targets are unchanged. #11406 includes a related preview correction within a broader navigation change; this PR isolates the icon inconsistency.
Verification
git diff --checkpassed.TestContext.bencherrors in untouchedsrc/performance.bench.ts; confirmed the same errors on unmodified upstream main.Before: header uses the primary checkout's red cloud, while the preview uses the remote checkout's automatic monogram.
After: header, preview, and picker defaults use the same representative.
GPT-6.1-Sol via the Codex harness in T3 Code.