git-clean-gone-branches

To delete local git branches after their remote is deleted, you identify them using git branch -vv to find gone-tracking entries, then prune them after confirming the list. This ensures your local repository stays clean and synchronized with the current remote state.

The best way to prune local branches with gone remotes is to read git branch -vv for gone-tracking entries and safely delete them after explicit user confirmation. This handles standard Git workflows in both single-repo and multi-branch environments, including those with associated worktrees.

Yes, pruning gone local branches works if the branches have associated worktrees. The process discovers local branches whose remote tracking branch has been deleted and safely deletes both the branches and their worktrees after you explicitly confirm the action.

Gone remote-tracking branches still show in your local repository because standard Git workflows leave local branches intact even after their remote counterparts are deleted. You can identify these gone branches using git branch -vv and remove them manually after explicit confirmation to reduce clutter.

Yes, you need to manually confirm before the script deletes gone branches and worktrees. The process prompts for explicit user confirmation before safely deleting any branches and their associated worktrees, providing live reporting during the removal to prevent accidental data loss.