gsd-remove-workspace

To safely remove a git worktree workspace, you must target each member repository individually and refuse removal if any repo has uncommitted changes. This ensures a safe, end-to-end workflow by verifying clean state before deletion.

If you attempt to remove a workspace with uncommitted changes in any member repository, the process refuses removal. This constraint prevents data loss by enforcing a clean working directory before executing git worktree remove operations.

The workspace removal process verifies safety by requiring user confirmation before destructive actions and delegating execution to a defined remove-workspace process. It checks each member repo for uncommitted changes to ensure a tidy environment.

You can automate the cleanup of multiple git worktrees by targeting a specified GSD workspace. The automated process iterates through member repositories, performing git worktree remove for each one to ensure proper cleanup.

The best way to clean up worktrees after a project ends is using an automated workflow that targets the specified workspace. It ensures all member repositories are properly cleaned up by running git worktree remove and requiring confirmation before acting.