Detached HEAD state in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What happens in Git when you enter a detached HEAD state?

In Git, what does it mean when you are in a detached HEAD state?

A You have checked out a specific commit, not a branch, so commits won't update any branch.

B Git has lost track of your repository and you cannot commit.

C You are on a branch and can commit changes normally.

D You are in a merge conflict state and must resolve conflicts before committing.

💡 Hint

Think about what HEAD points to when detached.

Detached HEAD means HEAD points directly to a commit, not a branch. Commits made here do not belong to any branch unless you create one.

💻 Command Output

intermediate

Output of git status in detached HEAD state

What is the typical output of git status when you have checked out a commit directly (detached HEAD)?

Git

git checkout 1a2b3c4d

git status

A

HEAD detached at 1a2b3c4d
nothing to commit, working tree clean

B fatal: You are not currently on a branch.

C

You are currently rebasing branch 'master' on 'origin/master'.
All conflicts fixed but you are still merging.

D

On branch master
Your branch is up to date with 'origin/master'.
nothing to commit, working tree clean

💡 Hint

Detached HEAD shows the commit hash in the status.

When HEAD is detached, git status shows 'HEAD detached at <commit>' and confirms the working tree is clean if no changes.

🔀 Workflow

advanced

How to save work done in detached HEAD state

You made commits while in a detached HEAD state. How do you save these commits to a branch so they are not lost?

A Run <code>git reset --hard HEAD~1</code> to save commits.

B Run <code>git checkout master</code> to automatically save commits to master.

C Run <code>git branch new-branch</code> to create a branch at the current commit.

D Run <code>git merge detached</code> to merge detached commits.

💡 Hint

Think about how to create a branch from the current commit.

Creating a branch at the current commit saves your work by giving it a branch name. Then you can switch to it anytime.

❓ Troubleshoot

advanced

Why does git push fail in detached HEAD state?

You are in a detached HEAD state and try to push your commits with git push origin HEAD. The push fails. Why?

A Because your remote repository is down.

B Because HEAD is not a branch, Git cannot push it without a branch name.

C Because you have uncommitted changes.

D Because you need to run <code>git fetch</code> first.

💡 Hint

Consider what HEAD points to in detached state and how push works.

Git push requires a branch name to update remote refs. Detached HEAD points to a commit, not a branch, so push fails without specifying a branch.

✅ Best Practice

expert

Best practice to avoid losing commits in detached HEAD

What is the best practice to avoid losing commits made in a detached HEAD state?

A Use <code>git stash</code> to save commits made in detached HEAD state.

B Reset HEAD to master after committing in detached HEAD state.

C Never commit in detached HEAD state; only commit on branches.

D Always create a new branch immediately after making commits in detached HEAD state.

💡 Hint

Think about how to keep commits safe and accessible.

Creating a branch after commits in detached HEAD ensures commits are referenced and not lost when switching branches.