Detached HEAD state in Git - Step-by-Step Execution

Process Flow - Detached HEAD state

Start on branch

↓

Checkout commit or tag

↓

HEAD points directly to commit

↓

Detached HEAD state active

↓

Make commits?

↓

Commits not on branch

↓

Switch back to branch to reattach HEAD

This flow shows how checking out a commit or tag moves HEAD away from a branch, creating a detached HEAD state where commits are not on any branch.

Execution Sample

Git

git checkout 1a2b3c4d
# Detached HEAD at commit 1a2b3c4d

git commit -m "temp change"
# Commit made but not on any branch

git checkout main
# HEAD reattached to branch main

This sequence shows checking out a commit causing detached HEAD, making a commit, then returning to a branch to reattach HEAD.

Process Table

Step	Command	HEAD points to	Branch	Notes
1	git checkout main	commit hash of main tip	main	HEAD attached to branch main
2	git checkout 1a2b3c4d	commit 1a2b3c4d	none	Detached HEAD state: HEAD points directly to commit
3	git commit -m "temp change"	new commit hash	none	Commit created but not on any branch
4	git checkout main	commit hash of main tip	main	HEAD reattached to branch main

💡 HEAD reattached to branch main, detached HEAD state ends

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4
HEAD	points to main branch tip	points to commit 1a2b3c4d (detached)	points to new commit (detached)	points to main branch tip (reattached)
Branch main	points to commit hash A	points to commit hash A	points to commit hash A	points to commit hash A

Key Moments - 3 Insights

Why does HEAD not point to any branch after 'git checkout 1a2b3c4d'?

Because you checked out a specific commit, not a branch name, so HEAD points directly to that commit, creating a detached HEAD state as shown in execution_table row 2.

What happens to commits made in detached HEAD state?

They are not on any branch and can be lost if you switch branches without saving them, as seen in execution_table row 3 where commit is made but branch remains unchanged.

How do you get out of detached HEAD state?

By checking out a branch again, which reattaches HEAD to that branch, shown in execution_table row 4.

Visual Quiz - 3 Questions

Look at the execution table, after which step is HEAD detached?

A After step 2

B After step 3

C After step 1

D After step 4

💡 Hint

Check the 'HEAD points to' and 'Branch' columns in execution_table row 2

At which step does HEAD reattach to a branch?

A Step 2

B Step 3

C Step 4

D Never

💡 Hint

Look at the 'Branch' column in execution_table row 4

If you make a commit in detached HEAD state and then switch branches without saving, what happens to that commit?

A It becomes part of the branch history

B It is lost unless referenced

C It merges automatically

D It deletes the branch

💡 Hint

Refer to key_moments answer about commits in detached HEAD state and execution_table row 3

Concept Snapshot

Detached HEAD state occurs when HEAD points directly to a commit, not a branch.
This happens by checking out a commit or tag.
Commits made here are not on any branch and can be lost.
To exit, checkout a branch to reattach HEAD.
Always save work before switching branches from detached HEAD.

Full Transcript

Detached HEAD state in git happens when you checkout a specific commit or tag instead of a branch. This causes HEAD to point directly to that commit, not to any branch. In this state, if you make commits, they are not part of any branch and can be lost if you switch branches without saving. To get out of detached HEAD state, you checkout a branch again, which reattaches HEAD to that branch. The execution table shows these steps clearly: starting on a branch, checking out a commit to detach HEAD, making a commit in detached state, and finally checking out the branch again to reattach HEAD.