Revisit delete confirmation UX for picker actions #171

New issue

Closed

opened 2026-04-12 17:22:07 +00:00 by barrettruth · 2 comments

barrettruth commented

2026-04-12 17:22:07 +00:00

Problem

Delete confirmations for branch/worktree actions currently use a numbered choice prompt.

That works, but it feels clunky compared to an inline [y/N] prompt.

Expected

a simpler inline confirmation style
an option to skip delete confirmations entirely for users who want faster picker workflows

## Problem Delete confirmations for branch/worktree actions currently use a numbered choice prompt. That works, but it feels clunky compared to an inline `[y/N]` prompt. ## Expected - a simpler inline confirmation style - an option to skip delete confirmations entirely for users who want faster picker workflows

barrettruth commented

2026-04-12 20:28:13 +00:00

Closing as done: branch/worktree delete confirmations already use inline [y/N] prompts, and / already allow skipping confirmations entirely. The current docs and specs also cover this behavior.

barrettruth commented

2026-04-12 20:28:22 +00:00

Closing as done: branch/worktree delete confirmations already use inline [y/N] prompts, and confirm.branch_delete / confirm.worktree_delete already allow skipping confirmations entirely. The current docs and specs also cover this behavior.

Closing as done: branch/worktree delete confirmations already use inline `[y/N]` prompts, and `confirm.branch_delete` / `confirm.worktree_delete` already allow skipping confirmations entirely. The current docs and specs also cover this behavior.