git-worktree-cleanup

You can automatically clean up git worktrees by running a script that identifies worktrees tied to merged branches or closed pull requests, deletes the worktrees and local branches, and prunes stale references. This prevents clutter and improves repository management.

Yes, you can remove git worktrees for squash merged branches. The cleanup process identifies and cleans up worktrees for branches associated with closed or merged pull requests, detecting squash merges to ensure the corresponding worktrees are deleted.

Yes, git worktree cleanup works with Azure DevOps. It updates Azure DevOps work items to a 'Resolved' state for branches that have been cleaned up, integrating repository management with project tracking via API interaction.

To automate git worktree deletion and branch pruning, you need bash scripting, Git commands, and interaction with GitHub and Azure DevOps APIs via MCP. These components identify merged branches, remove worktrees, delete local branches, and prune stale references.

Stale git worktrees accumulate when branches are merged or pull requests are closed without removing the associated worktrees. This happens frequently with squash merges where local branch references remain, requiring automated cleanup to prevent repository clutter.

The best way to prune stale git worktrees is to automate the cleanup process by checking pull request status and branch merge state. This approach removes unnecessary worktrees, deletes local branches, prunes stale references, and updates related work items simultaneously.