git-worktree-remove

To safely remove a git worktree, you execute a teardown command that enforces safety checks to protect main branches before deleting local and remote branches. This prevents accidental data loss during feature work cleanup.

The best way to clean up stale git worktree references is to use a structured removal process that prunes references automatically after deleting the worktree and its associated branches. This ensures your development environment remains clean.

Yes, removing a git worktree can delete local and remote branches when confirmed. The process applies safety checks first to prevent accidental deletion of main branches before removing the specified feature branches.

Git worktree cleanup requires database cleanup reminders because feature work environments often create related database entries that persist after worktree removal. Reminding users prevents stale data from accumulating in the database.

You should not use an automated git worktree removal process when working directly on main branches, as the safety checks are designed to protect them. If your worktree contains uncommitted changes, bypassing checks risks data loss.