Branches are just pointers

$ git branch

Two commits, one branch. main points at the latest commit, and HEAD points at main (the * in the list).

$ git branch soup

git branch soup sticks a new note onto the same commit. No files copied, no new commits — the graph barely changes.

$ git switch soup

git switch moves HEAD to soup. Both branches still point at the same commit, so your files do not change.

$ echo "Tomato soup: tomatoes, onion, basil" > soup.md
$ git add soup.md
$ git commit -m "Add tomato soup"

We commit on soup. Watch: only the soup note moved forward. main stayed behind, because HEAD was not pointing at it.

$ git switch main

Back on main. HEAD jumps back, and soup.md disappears from the working directory — main's snapshot doesn't have it. It is safe inside the soup commit.

$ echo "Waffles: flour, eggs, butter" > waffles.md
$ git add waffles.md
$ git commit -m "Add waffles"

A commit on main. History now forks: two branches grew in different directions from a common ancestor.

$ git switch -c dessert

git switch -c = create a branch and switch to it in one go. The most common way to start new work.

$ git switch main
$ git branch -d dessert

dessert had no unique commits, so deleting it is harmless. Deleting a branch removes the note, never the shared commits.

$ git branch -d soup

Git refuses to delete soup: its commit is not part of main, so the note is the only thing keeping it findable. -D would force it.