Repository navigation
Conversation
…474) Git before 2.36 has no 'worktree list -z', so the dialog showed no worktree rows on older Git. Scan activity once per preview, fingerprint only selected rows, keep refusals apart from partial failures, and tidy the row labels.
…474) The inventory takes a bounded share of the preview budget and marks late rows not inspected; a record that cannot be tied to a folder is shown once instead of marking every worktree uncertain.
…ive them the full budget (#474) An active tab, PTY or live CLI session with no known folder blocks every selected worktree again; dormant history only reports. Selected rows are inspected first with the remaining planner budget, and a failed inspection points to the dedicated Delete worktree action.
# Conflicts: # public/sidebar.js # src/main/projects/project-delete-main.js # src/main/projects/project-delete-plan.js # src/main/projects/project-delete.js # test/dom-project-delete.test.js
…le and follow worktree removal to the end (#474) The worktree activity read and the check before each removal use an isolated, per-preview process table instead of the shared cache, so a session started moments earlier cannot pass for stopped. The renderer's follow-up ceiling grows with the number of selected worktree folders.
…ds with main (#474) Each preflight and final per-folder check aborts its own process reads when it ends. Main and the renderer now share the worktree status, removal and directory-scan bounds, and the follow-up ceiling counts the scan and the post-failure inspection.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #474, slice E (Q3, maintainer decision 2026-11-10): the project-delete dialog also offers removing linked worktree folders from disk, each previewed and selected individually, unchecked by default. The main checkout and the project folder are never removable.
Behaviour
git worktree list --porcelain(newline format, works on Git before 2.36), parsed by the shared (worktrees): the delete dialog names the folder and forces only what it showed #841 parser. If the inventory fails, the dialog says why.node_modulesjunction) is inside it, or it is remote. An active session or schedule run whose folder is unknown blocks every selected folder. Activity and the check right before eachgit worktree removeread an isolated, per-preview process table; a stale or missing table is "unknown", never absence. Holds stop launches into the selected folders for the whole operation.Evidence
project-delete-worktrees*,dom-project-delete,project-delete-main,project-delete-plan,worktree-delete*), real-Git passing on Git 2.24.Not covered here: sibling worktrees of a whole repository are offered when the project is a subfolder of it (accepted).