Git Branch Delete Local Example |Video upload date:  · Duration: PT4M25S  · Language: EN

Learn how to safely delete local Git branches with commands checks and common gotchas explained in a short practical guide

If you have more feature branches than dignity, this guide shows how to delete local git branches the smart way. You will learn how to check your context, list branches, delete branches safely, and force delete when you absolutely mean it. No hand holding, just clear git commands and a tiny amount of moral support.

Check current branch before deleting

Deleting the branch you are currently on is a quick path to unhappy surprises. Confirm your branch with one of these git commands, whatever fits your workflow.

git status
# or
git branch

If git status says you are on main or develop then you are safe to remove other branches. If it says the name of the branch you want to delete, switch off it first by checking out a safe branch.

git checkout main

List local branches and check merge status

Names matter. Typing the wrong branch name is the typo driven calamity everyone fears. First list local branches, then see which ones are merged into your current branch.

git branch
# show branches merged into the current branch
git branch --merged
# show branches not yet merged
git branch --no-merged

Use --merged and --no-merged to decide whether the branch is safe to delete or still holding unmerged commits.

Delete branch safely

When git can tell that your work has been incorporated into the current branch, it lets you delete politely. This avoids accidental loss of commits.

git branch -d feature-name

The -d flag refuses to delete a branch that is not merged. That is git showing common sense where humans sometimes do not.

Force delete when necessary

If the branch is experimental, abandoned, or you have already pushed and archived the commits elsewhere, use force delete. This obliterates the local ref immediately, so double check before you press enter.

git branch -D feature-name

Use -D only when you know the commits are expendable or safely backed up on a remote or another branch. This is a tool, not a therapy session.

Make a quick backup branch if you are unsure

Not sure if you will regret deleting the branch? Create a local backup branch as a restore point. It takes seconds and your future self will thank you, or at least stop yelling at you.

git branch backup/feature-name feature-name

That creates backup/feature-name pointing at the same commits so you can delete the original branch and still recover later.

Tips for recovery and extra safety

  • Use git reflog to find recent commits and recover a deleted branch if needed.
  • If you find the commit hash, recreate the branch with git checkout -b feature-name COMMIT_HASH where COMMIT_HASH is the SHA.
  • When working with a remote, consider deleting the remote branch separately with git push origin --delete feature-name after confirming local cleanup.

Quick checklist before deleting a local branch

  • Confirm you are not on the branch, use git status or git branch
  • Verify merge status with git branch --merged or --no-merged
  • Create a backup branch if you think you might change your mind
  • Use git branch -d for polite deletion, use git branch -D only when you are sure

There you go, a tidy, slightly sarcastic walkthrough for deleting local branches with minimal drama. Follow these git commands and you will keep your local-branch list neat, avoid accidental data loss, and preserve your developer reputation just enough to keep getting invited to code reviews.

I know how you can get Azure Certified, Google Cloud Certified and AWS Certified. It's a cool certification exam simulator site called certificationexams.pro. Check it out, and tell them Cameron sent ya!

This is a dedicated watch page for a single video.