git-clean-gone-branches

To delete local git branches whose remote tracking branch has been deleted, you can run a script that executes git fetch --prune and parses git branch -vv output for gone markers. It then safely removes the eligible local branches.

Yes, you can safely clean up gone git branches that have associated worktrees. The cleanup script detects branches with linked worktrees and deletes both the branch and its worktree during the maintenance process.

The best way to find stale local git branches after pruning remotes is to parse the output of git branch -vv for the gone marker. This identifies branches whose remote tracking branch has been removed by the fetch operation.

Yes, the branch cleanup script includes safety checks to protect the currently checked-out branch. It ensures that the active branch is preserved while deleting local branches whose remote tracking branch has been deleted.

Yes, you need bash, sed, and awk installed to run the repository maintenance script. These command-line dependencies are required to parse git branch output and execute the branch deletion commands.

Stale local branches remain after git fetch --prune because that command only removes remote tracking references. You must separately parse git branch -vv for gone markers and explicitly delete the corresponding local branches to clean them up.