Detached HEAD state in Git - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the phrase from `git status` output indicating detached HEAD state.

Git

HEAD detached at [1]

Drag options to blanks, or click blank then click option'

Amaster

Btag

Cbranch

Dcommit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'master' or 'branch' which are branch names, not commit references.

Confusing 'tag' with commit in detached HEAD context.

The phrase 'HEAD detached at commit' indicates that HEAD points directly to a commit, not a branch.

2fill in blank

medium

Complete the command to create a new branch from the current detached HEAD state.

Git

git checkout -b [1]

Drag options to blanks, or click blank then click option'

Anew-branch

BHEAD

Cmaster

Dorigin

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'HEAD' as branch name which is invalid.

Trying to checkout 'master' which switches to an existing branch.

To save work from a detached HEAD, create a new branch with a name like 'new-branch'.

3fill in blank

hard

Fix the error in the command to return to the main branch from a detached HEAD state.

Git

git checkout [1]

Drag options to blanks, or click blank then click option'

Acommit

Bmain

Cdetached

DHEAD

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'HEAD' which keeps you in detached state.

Using 'commit' which is not a branch.

To leave detached HEAD and return to the main branch, checkout 'main'.

4fill in blank

hard

Fill both blanks to create a new branch and switch to it from a detached HEAD.

Git

git [1] -b [2]

Drag options to blanks, or click blank then click option'

Acheckout

Bcommit

Cnew-branch

Dreset

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'commit' or 'reset' as commands which do not create branches.

Using 'commit' as branch name which is invalid.

'git checkout -b new-branch' creates and switches to a new branch from detached HEAD.

5fill in blank

hard

Fill all three blanks to discard changes and return to the main branch from detached HEAD.

Git

git [1] --hard [2] && git [3] main

Drag options to blanks, or click blank then click option'

Areset

BHEAD

Ccheckout

Dcommit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'commit' instead of 'checkout' to switch branches.

Using 'commit' instead of 'HEAD' in reset command.

This sequence resets changes to HEAD and then checks out the main branch.

Practice

1. What does it mean when Git is in a detached HEAD state?

easy

A. You are merging two branches together.

B. You are on the latest commit of the main branch.

C. You are viewing a specific commit, not a branch.

D. You have uncommitted changes in your working directory.

Solution

1. Step 1: Understand HEAD in Git

   HEAD usually points to the latest commit on a branch, representing your current working state.

2. Step 2: Meaning of detached HEAD

   When HEAD points directly to a commit instead of a branch, you are in detached HEAD state, meaning you are not on any branch.

3. Final Answer:

   You are viewing a specific commit, not a branch. -> Option C

4. Quick Check:

   Detached HEAD = viewing commit, no branch [OK]

Hint: Detached HEAD means no branch, just a commit [OK]

Common Mistakes:

• Confusing detached HEAD with uncommitted changes
• Thinking detached HEAD means merging branches
• Assuming detached HEAD is always on main branch

2. Which Git command puts you into a detached HEAD state?

easy

A. git checkout main

B. git branch new-feature

C. git merge feature-branch

D. git checkout

Solution

1. Step 1: Understand git checkout usage

   Checking out a branch moves HEAD to that branch's latest commit, staying attached.

2. Step 2: Checkout a commit hash

   Checking out a specific commit hash moves HEAD directly to that commit, causing detached HEAD state.

3. Final Answer:

   git checkout <commit-hash> -> Option D

4. Quick Check:

   Checkout commit hash = detached HEAD [OK]

Hint: Checkout commit hash, not branch, to detach HEAD [OK]

Common Mistakes:

• Using branch name instead of commit hash
• Confusing branch creation with checkout
• Thinking merge causes detached HEAD

3. What will be the output of the following commands?

git checkout 1a2b3c4
git status

Assuming 1a2b3c4 is a valid commit hash.

medium

A. HEAD detached at 1a2b3c4
nothing to commit, working tree clean

B. On branch main
Your branch is up to date.

C. error: pathspec '1a2b3c4' did not match any file(s) known to git

D. You are currently rebasing branch 'main'

Solution

1. Step 1: Checkout commit hash

   Running git checkout 1a2b3c4 moves HEAD to that commit, entering detached HEAD state.

2. Step 2: Check git status output

   In detached HEAD, git status shows 'HEAD detached at <commit>' and clean working tree if no changes.

3. Final Answer:

   HEAD detached at 1a2b3c4 nothing to commit, working tree clean -> Option A

4. Quick Check:

   Detached HEAD status shows commit and clean tree [OK]

Hint: Detached HEAD status shows commit hash and clean tree [OK]

Common Mistakes:

• Expecting branch name in status
• Thinking checkout commit hash causes error
• Confusing rebase message with detached HEAD

4. You are in detached HEAD state and made some changes. Which command will save your changes safely on a new branch?

medium

A. git commit -m 'save changes'

B. git checkout -b new-branch

C. git merge main

D. git reset --hard

Solution

1. Step 1: Understand detached HEAD changes

   Changes made in detached HEAD are not on any branch and can be lost if you switch commits.

2. Step 2: Create a new branch to save changes

   Using git checkout -b new-branch creates a branch at current commit and switches to it, preserving changes.

3. Final Answer:

   git checkout -b new-branch -> Option B

4. Quick Check:

   Create branch from detached HEAD to save changes [OK]

Hint: Create new branch from detached HEAD to keep changes [OK]

Common Mistakes:

• Committing without a branch loses changes on checkout
• Merging without branch context does not save changes
• Resetting discards changes

5. You checked out a commit hash and made changes in detached HEAD. Later, you want to keep those changes and continue working on a branch named feature. What is the correct sequence of commands?

hard

A. git checkout -b feature
git add .
git commit -m 'work'

B. git commit -m 'work'
git branch feature
git checkout feature

C. git add .
git commit -m 'work'
git checkout feature

D. git checkout feature
git merge HEAD

Solution

1. Step 1: Create and switch to new branch

   Use git checkout -b feature to create a branch at current detached HEAD and switch to it.

2. Step 2: Stage and commit changes

   Run git add . and git commit -m 'work' to save your changes on the new branch.

3. Final Answer:

   git checkout -b feature git add . git commit -m 'work' -> Option A

4. Quick Check:

   Create branch first, then commit changes [OK]

Hint: Create branch first, then add and commit changes [OK]

Common Mistakes:

• Committing before creating branch loses changes
• Switching to branch before committing loses detached changes
• Merging detached HEAD into branch is incorrect