clean-gone

To remove local git branches marked as gone, you can run a cleanup process that detects stale local branches reflecting remote deletions and deletes them. This ensures your local repository matches the remote state by clearing out branches that no longer exist upstream.

[gone] branches are local git branches whose remote counterparts have been deleted, causing them to accumulate locally and clutter your repository. They are labeled [gone] by git when tracking remote branches that no longer exist, creating confusion and slowing development.

Yes, branch cleanup can remove git worktrees associated with deleted branches. The process identifies any worktrees linked to [gone] branches and removes them to ensure complete cleanup, handling both branches with and without associated worktrees.

The best way to automate git worktree and branch cleanup in one step is to use a cleanup tool that runs standard git commands to detect, remove worktrees, and delete corresponding [gone] branches. This allows developers to prune all local remnants after a remote branch deletion simultaneously.

No, you do not need specific git plugins to delete stale local branches and worktrees. The cleanup process requires only standard git commands, specifically git branch and git worktree, to detect and remove branches marked as [gone] and their associated worktrees.