stale-branch-audit

You can audit branches older than 30 days, merged branches with no worktree, orphaned worktrees, and branches with a deleted remote. The audit generates a prioritized cleanup list to safely prune stale branches without accidental deletion.

A stale branch is typically a local or remote branch older than 30 days, a merged branch with no active worktree, an orphaned worktree, or a branch tracking a deleted remote, all of which clutter the repository and require cleanup.

Yes, you can batch audit stale branches across multiple repositories as specified by your input, identifying merged branches and orphaned worktrees to produce a unified, prioritized cleanup list for repository management.

To avoid accidental deletion, the audit checks for branches pinned by an active worktree and generates a prioritized cleanup list, separating branches ready for pruning from those that still need manual review.

You need basic Git operations and an understanding of the branch lifecycle to identify orphaned worktrees and branches with a deleted remote, ensuring safe repository cleanup based on the provided audit list.

You should run a branch audit when repository management becomes cumbersome, checking for branches older than 30 days, merged branches lacking worktrees, or orphaned worktrees to maintain a clean Git environment.