Introduction

Cleaning up old remote Git branches usually means two different tasks that people often mix up. One is deleting stale branch references from your local clone. The other is actually deleting branches from the remote repository. Those are related, but they are not the same operation, and confusing them is how teams accidentally delete branches they only meant to hide locally.

Remove Stale Remote-Tracking References Locally

If a branch was already deleted on the remote, your local clone may still show the old remote-tracking reference until you prune it.

git fetch --prune

That tells Git to fetch updates and remove local origin/... references that no longer exist on the remote server.

You can inspect what remote branches you currently know about with:

git branch -r

This is the safe first step because it does not delete anything on the remote. It only makes your local view accurate.

Delete A Branch On The Remote

If you really want to remove a branch from the remote repository itself, use:

git push origin --delete feature/old-experiment

That sends a deletion request to the remote named origin.

Only do this when you are sure the branch is no longer needed. Deleting a remote branch affects the team, not just your own clone.

Identify Old Branches Before Deleting Them

A useful inspection command is:

git for-each-ref --sort=-committerdate refs/remotes/origin/ \
  --format='%(committerdate:short) %(refname:short)'

This shows remote-tracking branches sorted by recent activity, which helps you spot branches that have not moved in a long time.

That is still just reporting. It is a safer way to review than jumping directly into deletion.

Protect Important Branches

Before deleting anything, confirm that branch protection or team workflow does not rely on it.

Common branches to avoid touching casually are:

• 'main'
• 'master'
• 'develop'
• release branches still in use
• branches with open pull requests

A branch that looks stale locally may still back an active code review or deployment workflow.

Cleaning Up After Merges

A normal cleanup workflow after a pull request merge is:

git fetch --prune
git branch -r

and then, if a remote feature branch should be removed:

git push origin --delete feature/my-branch

After that, other developers can run git fetch --prune to update their local remote-tracking references.

Local Branches Are Separate

Deleting a remote branch does not automatically remove your local branch.

git branch -d feature/my-branch

or, if Git warns the branch is not merged and you intentionally still want it gone:

git branch -D feature/my-branch

That is separate from the remote cleanup.

Use Automation Carefully

Teams often want scripts to delete stale branches automatically, but branch age alone is a weak signal. A branch may be old because it is stable, paused, or still under review.

The safest automation is usually reporting and candidate listing, not blind deletion.

Common Pitfalls

The most common mistake is thinking git fetch --prune deletes branches from the remote. It does not. Another is deleting remote branches without checking whether a pull request or release process still depends on them. Developers also sometimes remove the remote branch and forget that teammates will still see stale references until they fetch with prune. Finally, local branch deletion and remote branch deletion are separate operations and should be treated deliberately.

Summary

• 'git fetch --prune cleans up stale remote-tracking references in your local clone.'
• 'git push origin --delete branch-name deletes an actual branch from the remote.'
• Review age and usage before deleting remote branches.
• Protected, release, and review branches need extra caution.
• Local branch cleanup is a separate step from remote branch cleanup.