setup: hide the restore card until rt restore exists - #414
Conversation
Its Continue ran rt restore, which rt does not have, so choosing it failed with unknown command. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
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: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour. 📝 WalkthroughWalkthroughThe team-choice screen no longer displays the “Already have mattstack settings?” restore card. The create and join cards remain. ChangesTeam Choice Screen
Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to Users can choose Create or Join; the unavailable restore option is hidden as intended. No concrete merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
The team screen's "Already have mattstack settings?" card runs
rt restore <org>/<repo>at Continue. rt has norestorecommand (rt restore --helpprints "unknown command: restore"), so picking it was a dead end.TeamScreen.TeamChoiceModel's restore path and the card's fields stay in place for when the command exists; nothing else can preselect.restore(the model defaults to.create).Verified:
swift buildclean. Rendered the team screen from this build in light and dark: two cards (Create, Join), nothing clipped. No test or VM driver references the restore card.🤖 Generated with Claude Code
Summary by CodeRabbit