clean-branches

To delete stale local git branches, you can fetch with pruning to detect branches marked as [gone] and force-delete them locally. This removes branches that were deleted on the remote but still exist in your local repository.

Cleaning up git worktrees involves detecting those linked to stale branches and force-removing them. This prevents lingering worktree directories from cluttering your development setup after remote deletions.

Repository hygiene in a monorepo with multiple worktrees requires fetching with pruning to identify [gone] branches. You then safely remove associated worktrees and force-delete the stale branches to prevent local drift.

Local branches still show up because remote deletions do not automatically sync to your local repository. You must fetch with pruning to detect them as [gone] and explicitly remove them to clean up the local state.

It is safe to force delete stale branches when the process specifically targets [gone] branches and avoids removing the current top-level worktree. This ensures active branches and your current working directory are protected from accidental deletion.