cleanup-local-branches

Automatically delete stale local Git branches by running a cleanup workflow that checks remote tracking status and inactivity thresholds, removing branches gone from the remote origin or inactive for over six months.

Git branch pruning identifies orphaned local branches by checking remote tracking status against the origin repository and applying inactivity thresholds to flag branches no longer existing remotely or inactive for over six months.

Yes, you can safely clean up local Git branches without losing unmerged work using safety-checked deletion that performs patch-identity verification and provides a full preview before any deletion occurs.

The best way to prune dead Git branches after merging pull requests is to automate identification and deletion of orphaned local branches using remote tracking status and inactivity thresholds with safety-checked deletions.

Yes, you need git CLI access to automate local branch cleanup because the pruning workflow uses git commands to verify remote tracking status and perform safety-checked deletions using patch-identity verification.

Limitations when pruning inactive Git branches automatically include protection of your current branch, default branches, and active work, meaning the workflow will not delete branches currently checked out or serving as the repository default.