naps62/maestro
Archived
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

spawn form: the branch field's label duplicates the mode radios #94

New Issue
Closed
opened 2026-08-24 14:28:12 +01:00 by naps62-yolo · 0 comments
naps62-yolo commented 2026-08-24 14:28:12 +01:00
Collaborator
Copy Link
Copy Source

With the worktree section open the box currently reads:

☐ Create git worktree
  ( ) New branch   ( ) Existing branch
  Branch [________]

Three controls say "branch" and none of them says which. The field labelled Branch is the new branch name in one mode and an existing branch picker in the other; both are literally <label>Branch</label> in the markup (.wt-new-wrap and .wt-exist-wrap), with one hidden at a time. Reading the form, you cannot tell what the field wants.

Make the label say what the field is in the mode it belongs to — the new-branch input and the existing-branch select need distinct, self-explanatory labels — or drop the mode radios and let one control carry both meanings.

Whichever way it goes, the same wording applies to the TUI draft pane so the two clients do not describe the same field differently.

Depends on: the worktree-collapse issue, which edits the same fieldset markup.

With the worktree section open the box currently reads: ``` ☐ Create git worktree ( ) New branch ( ) Existing branch Branch [________] ``` Three controls say "branch" and none of them says which. The field labelled `Branch` is the *new branch name* in one mode and an *existing branch picker* in the other; both are literally `<label>Branch</label>` in the markup (`.wt-new-wrap` and `.wt-exist-wrap`), with one hidden at a time. Reading the form, you cannot tell what the field wants. Make the label say what the field is in the mode it belongs to — the new-branch input and the existing-branch select need distinct, self-explanatory labels — or drop the mode radios and let one control carry both meanings. Whichever way it goes, the same wording applies to the TUI draft pane so the two clients do not describe the same field differently. Depends on: the worktree-collapse issue, which edits the same fieldset markup.
naps62-yolo added this to the Spawn v2 milestone 2026-08-24 14:28:12 +01:00
naps62-yolo added the area/tuiarea/webtype/fixdifficulty/easy labels 2026-08-24 14:28:12 +01:00
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/android
area/cli
area/config
area/daemon
area/protocol
area/tui
area/web
code-review
difficulty/easy
difficulty/hard
difficulty/medium
epic
Tracks a multi-issue epic / parent work item
 tui
type/docs
type/feat
type/fix
type/refactor
type/test
No labels area/tui area/web difficulty/easy type/fix
Milestone
No items
No Milestone Spawn v2
Projects
Clear projects
No projects
Assignees
Clear assignees
hermes (Hermes (agent)) naps62-yolo (naps62-yolo (agent)) resende (Resende) naps62 (Miguel Palhas)
No Assignees
1 Participants
Due Date
No due date set.
Depends on
#93 spawn form: collapse the worktree section, closed by default
naps62/maestro
Reference: naps62/maestro#94