git branch Tutorial

What you will learn

• Understand the core purpose of git branch Tutorial
• Master the basic usage and common options of git branch Tutorial
• Covers how git branch lists, creates, renames, and deletes branches, and how it relates to remote-tracking branches.
• Understand key concepts: Listing branches
• Know when to use this feature and when to avoid it

Start with a problem

You're working in a Git repository and need to perform a specific task — but you're not sure which command or option is the right fit, or what this command can and cannot do.

The short version

git branch manages branch refs, which are names that point at commits.

Listing branches

git branch
git branch -r
git branch -a
git branch -vv

-vv is especially useful because it shows upstream tracking information and the latest commit summary.

Creating a branch

git branch feature/login

This creates the branch but does not switch to it. For that, pair it with git switch -c or use the older checkout form.

Renaming and deleting

git branch -m old-name new-name
git branch -d feature/login

Use -D only when you deliberately want a force delete.

Local vs remote-tracking refs

People often confuse main with origin/main. The first is your local branch. The second is a remote-tracking ref updated by fetch. Understanding that distinction helps explain many sync workflows.

What problem this command solves in a workflow

git branch operates at the reference layer, responsible for creating, renaming, listing, and deleting branches. It does not touch working tree content or the staging area — its core duty is managing "names that point at commits," letting you organize work across different development lines.

Typical use cases

• Use git branch to list all local branches and quickly understand what development lines exist.
• Use git branch -vv to see each branch's upstream tracking relationship and latest commit — a frequent pattern for diagnosing sync status.
• Use git branch -d to safely delete already-merged branches and keep the branch list tidy; confirm you want a force delete with -D.

Diagram view

Input

Branch nameTarget commit (when creating)Current HEAD

→git branch

Output

New ref under refs/heads/Updated branch listDeleted refs

branch only manages the refs themselves; use switch/checkout to switch branches and merge/rebase to integrate changes.

Special cases and boundaries

• git branch creates branch refs only; it does not switch to them — use git switch for that.
• Deleting a branch does not delete commits: as long as other refs or the reflog still point at them, the commit objects remain.
• git branch -d refuses to delete unmerged branches as a safety measure; use -D to force when you are sure.
• Remote-tracking refs (e.g., origin/main) and local branches (e.g., main) are independent: fetch updates the former, and you need merge or rebase to integrate into the latter.

Try it yourself

1. Practice the git-branch command in a test repository and observe state changes before and after
2. Experiment with different options and compare the output differences
3. Simulate a real scenario where you would need to use this, and walk through the full process

Further reading

Keep going on the same topic:

• git blame
• git-bundle Tutorial
• git-cat-file Tutorial