pingdotgg / pingdotgg/t3code

Deleting multiple threads asks about each orphaned worktree in a separate dialog

Open
#7,067 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Selecting several threads in the sidebar and choosing Delete confirms the batch once, then asks "delete the worktree too?" separately for every selected thread that has one. Worse, the deletion for the previous row runs before the next dialog appears, so clearing ten threads means answering the same question ten times with a couple of seconds of dead air in between.

Steps to reproduce
  1. Create several threads, each with its own worktree.
  2. Multi-select them in the sidebar and pick Delete.
  3. Confirm the "Delete N threads" dialog.
Current behavior

Seven threads selected, each with its own worktree:

Multi-select context menu

Delete 7 threads confirmation

Then the same question, once per thread, with a deletion round trip in between:

Worktree prompt for wt-6

Worktree prompt for wt-5

Worktree prompt for wt-4

Suggested behavior

Count the worktrees the whole selection would orphan, ask once, and apply that single answer to every deletion. A worktree should only count when every thread pointing at it is inside the selection. Single-thread deletes keep the existing per-thread prompt.

Bulk worktree prompt

All seven threads deleted

Fixed by #6594.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the bulk thread-deletion flow described in the issue and compare it with the fix in #6594. Verify that selected threads sharing orphaned worktrees produce one prompt, while single-thread deletion retains its existing prompt; confirm the behavior by reproducing the multi-select scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.