Per spec item 24 (P0, V1, not built). dot deploy should default to moddable, and walk a user who isn't set up for it through GH login + creating their own public repo, rather than 403-ing against the cloned source.
Target flow:
dot deploy → prompt defaults Y/n moddable (currently effectively n/Y because moddable fails)- If user accepts and has no user-owned GH remote: CLI prompts GH login (only if not already logged in), then offers to create a public repo on their account
- Push goes to the user's repo, not back to canonical
--no-moddable remains the escape hatch
Spec receipts:
- A3 Moddable (P0): default moddable, GitHub login not required to deploy (i.e. only required if the user opts into moddable)
- Item 24: "Full guided flow with user-initiated repo creation option"
- Error rewrite (UI copy section): "Create a public GitHub repo, push your code, then re-run. Or use
--no-moddable to skip this."
Symptom this resolves: #75 — user gets a 403 pushing to paritytech/Rock-Paper-Scissors because the current code path assumes write access to the cloned origin instead of routing them to their own repo.
Per spec item 24 (P0, V1, not built).
dot deployshould default to moddable, and walk a user who isn't set up for it through GH login + creating their own public repo, rather than 403-ing against the cloned source.Target flow:
dot deploy→ prompt defaults Y/n moddable (currently effectively n/Y because moddable fails)--no-moddableremains the escape hatchSpec receipts:
--no-moddableto skip this."Symptom this resolves: #75 — user gets a 403 pushing to
paritytech/Rock-Paper-Scissorsbecause the current code path assumes write access to the cloned origin instead of routing them to their own repo.