branch-cleanup

This workflow identifies and safely deletes local and remote branches already merged into your main or master branch. It presents a clear list of candidate branches and requires explicit confirmation before performing any deletions.

No, the cleanup process explicitly avoids protected branches like main and master. It safely removes only the merged feature branches while ensuring your primary main or master branches are never deleted.

Yes, the workflow detects and removes both local branches and remote-tracking branches that are stale or merged. It presents a unified list of candidates for explicit confirmation before deleting them simultaneously.

The safest way to delete Git branches is using a workflow that requires explicit user confirmation before deletion. This process identifies only merged branches, lists candidates clearly, skips protected branches, and generates a report of what was deleted and skipped.

To identify which Git branches are safe to delete, look for branches that have been merged into main or master. The workflow automatically lists these candidates, avoids protected branches, and requires explicit confirmation before proceeding.