git-clean-gone-branches

To clean up local git branches whose remote tracking branch is gone, you can run a discovery script to fetch the latest remote state and identify stale branches. The tool then requires a single confirmation to safely delete all listed branches.

Yes, git branch cleanup removes any linked worktrees. When deleting confirmed gone branches, the process automatically handles and removes any associated worktrees to ensure a complete and safe cleanup of the local repository.

The best way to find stale git branches is to run a discovery script that fetches the latest remote state and identifies local branches whose origin tracking is gone. This approach is applicable when cleaning up stale branches across multiple repositories.

Yes, deleting gone branches is safe because the process uses a two-stage workflow that respects the current branch. It first discovers gone branches and then requests a single user confirmation before performing an atomic deletion of all listed branches.

Yes, you need git installed to prune local branches with no remote. The discovery script relies on git to fetch the latest remote state, identify branches whose origin tracking is gone, and safely remove any associated worktrees.

Git keeps local branches because remote deletions do not automatically propagate to your local environment. You must explicitly fetch the latest remote state, identify the gone branches, and confirm their deletion locally to clean up the stale references.