Introduction

Git does not let you delete the branch you are currently checked out on. To remove it, you must first switch to a different branch, then delete the old branch by name.

Why Git Blocks This

A branch is just a movable reference to a commit, but your working tree and HEAD also point at the branch you currently have checked out. Deleting that branch while it is active would leave the repository in an ambiguous state, so Git refuses the operation.

If you try anyway, Git prints an error telling you the branch is currently checked out.

Switch to Another Branch First

The normal workflow is:

git switch main
git branch -d feature/login

If your Git version does not support git switch, the older equivalent is:

git checkout main
git branch -d feature/login

The -d flag deletes the branch only if Git believes the branch has already been safely merged.

Force Delete When You Intend to Drop Work

If the branch contains commits that are not merged and you still want to remove it, use -D:

git switch main
git branch -D feature/login

That is a force delete. It is useful for abandoned experiments, but you should use it deliberately because it can hide work that is hard to recover later.

What If You Have Uncommitted Changes

Sometimes the real blocker is not branch deletion but the branch switch. If your current branch has uncommitted changes that would be overwritten, Git may refuse the checkout or switch.

In that case, either commit the changes, stash them, or discard them intentionally before moving away:

git stash push -m "temporary save before deleting branch"
git switch main
git branch -d feature/login

Stashing is helpful when you want a safety net before cleanup.

Deleting the Remote Branch Too

Removing a local branch does not delete the remote branch on origin. If you also want to delete the remote reference, run:

git push origin --delete feature/login

After that, teammates may still see stale tracking references until they fetch or prune:

git fetch --prune

That command cleans up remote-tracking branches your local repository still remembers.

A Safe Cleanup Pattern

If you want a predictable routine, use this sequence:

1git switch main
2git pull
3git branch --merged
4git branch -d feature/login

git branch --merged helps you verify that the branch you are about to delete is already merged into your current branch. That reduces the chance of deleting something important accidentally.

Recovering from a Mistake

If you delete the wrong branch locally, recovery may still be possible through the reflog:

git reflog

Once you find the relevant commit, recreate the branch:

git branch feature/login <commit-hash>

This is another reason force deletion is not always catastrophic, but it is still better to avoid relying on recovery.

Common Pitfalls

• Trying to delete the branch you are currently on. Git will block it every time.
• Using -D when -d would have warned that the branch was not merged.
• Forgetting that local and remote branch deletion are separate actions.
• Switching branches with uncommitted changes and assuming Git will always allow it.
• Deleting a branch without confirming it was merged into the branch that matters for your workflow.

Summary

• You cannot delete the currently checked-out Git branch directly.
• Switch to another branch first, then use git branch -d branch-name.
• Use git branch -D branch-name only when you intentionally want to force deletion.
• Delete the remote branch separately with git push origin --delete branch-name.
• Check merge status and stash or commit local changes before cleanup.