sync

To prune stale git branches and worktrees after merging a PR, you need to fetch remote updates with pruning enabled, detect obsolete local branches, and safely delete them. This process removes unused worktrees and aligns your local repository state with the remotes.

The best way to keep a local git repository clean across multiple remotes is to regularly fetch and prune remote-tracking refs, remove stale local branches, and pull updates on remaining branches. This ensures a clean working state reflecting true remote conditions.

Git fetch prune works by querying remotes to identify and delete remote-tracking refs that no longer exist on the remote server. It then detects corresponding obsolete local branches and stale worktrees, removing them safely without affecting active work.

Yes, you can automatically delete stale worktrees without affecting active development branches. The sync mechanism identifies stale local branches and their associated worktrees, safely removing only the obsolete ones while pulling updates on the remaining active branches.

Your local git branch still shows up after remote deletion because your local repository retains stale remote-tracking refs until a prune is executed. Running a fetch with prune removes these obsolete refs and safely deletes the corresponding stale local branches.

You should run a git worktree and branch cleanup after merging a PR or finishing a feature. This repository cleanup fetches and prunes remotes, removes stale worktrees, deletes obsolete branches, and pulls updates to maintain a clean working state.