Delete-Merged-Branches

Deleting merged remote branches safely requires filtering GitHub PR data by a merged state, excluding protected branches, running in dry-run mode by default, and requiring explicit confirmation before calling the Git refs delete endpoint.

Yes, you can clean up git branches without losing pull request artifacts by targeting only branches with PRs in the merged state, which preserves the original PR data and commit history while removing obsolete remote refs.

The best way to automate git branch cleanup for merged pull requests is to use a workflow that filters by merged PR state, excludes protected branch names and the current branch, and presents a candidate list for explicit user confirmation before deletion.

Yes, the remote branch deletion process includes safety guardrails that filter out and skip protected branch names as well as the current working branch to prevent accidental deletion of active development lines.

Yes, you need to review a dry-run list because the deletion workflow runs in dry-run mode by default, presenting a candidate list of merged branches and requiring your explicit confirmation before executing the actual deletion.