clean-all

To delete all local and remote Git branches except main, you can use an automated cleanup tool that removes non-main branches, prunes stale remote-tracking references, and clears associated worktree directories to ensure a clean repository state.

The best way to clean up stale Git branches after merging a feature is to automate the deletion of non-main branches both locally and remotely, while pruning outdated remote-tracking references and removing linked worktree directories.

Git remote pruning works by removing stale remote-tracking branches that no longer exist on the remote server, ensuring your local repository references are synchronized and free of outdated branch clutter.

Yes, you can automatically remove Git worktrees when cleaning up repository branches by running a cleanup process that deletes associated worktree directories alongside non-main local and remote branches.

You should not use an automated tool to delete Git branches if you have unmerged changes or active feature branches, as this process permanently deletes all non-main branches locally and remotely without selective recovery options.

No dependencies are required to clean up Git branches automatically, as the cleanup process runs directly within your Git environment to delete non-main branches, prune remote references, and remove worktree directories.