gsd-remove-workspace

Removing a workspace fails safely and aborts the operation if any member repository has uncommitted changes. This safety check prevents data loss by ensuring all work is committed before worktrees are torn down.

You need workspace cleanup when tearing down obsolete or test workspaces in multi-repo setups. Removing worktrees and deleting the workspace prevents leftover configurations, avoids confusion, and keeps your repository structure clean.

If a repository has uncommitted changes, the workspace removal process will abort. This safety check prevents data loss by ensuring no uncommitted work is accidentally discarded during the git worktree removal step.

Yes, you need to confirm the workspace name before deleting a GSD workspace. Workspace name validation and explicit user confirmation are required safeguards to ensure the correct workspace and its associated worktrees are targeted for removal.

Yes, you can remove multiple worktrees from a multi-repo setup at once by running the remove-workspace command. It executes git worktree remove for every member repository, ensuring each worktree is removed before the workspace itself is deleted.