ce-clean-gone-branches

To clean up local git branches that are gone remotely, you can use a script that runs git fetch --prune and parses git branch -vv to identify branches whose remote tracking branch has been deleted. It then asks for confirmation and removes the confirmed branches.

The best way to delete stale local branches and their worktrees is to detect them by fetching remote state and identifying branches marked as gone in git branch -vv. Any associated worktrees are removed prior to branch deletion to ensure safe cleanup.

Yes, git fetch --prune works across single or multiple remotes. When removing gone branches, the process applies to development workflows with stale branches and worktrees, ensuring any associated worktrees are removed before the branches are deleted.

You can safely remove local branches because the process asks for confirmation before deleting any branches. It identifies gone branches by parsing git branch -vv after fetching remote state, giving you control over which branches are deleted.

After running git fetch --prune, you still see local branches because git only removes remote tracking references, not local branches. You need to additionally parse git branch -vv to identify branches marked as gone and explicitly delete them.