HEAD pointer concept in Git - Commands & Configuration

Introduction

When you work with Git, HEAD is like a bookmark that shows which version of your project you are currently looking at or working on. It helps Git know where you are in your project's history so you can make changes or look at past versions easily.

When you want to see which branch or commit you are currently working on.

When you want to switch to a different branch or commit in your project.

When you want to create a new branch starting from your current position.

When you want to understand why your changes are not appearing as expected.

When you want to reset your working files to a previous state.

Commands

This command shows the current branch and the state of your working directory. It tells you where HEAD is pointing by showing the branch name.

Terminal

git status

Expected Output

On branch main

Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean

This command lists all branches and marks the one where HEAD currently points with an asterisk (*).

Terminal

git branch

Expected Output

* main

  feature-1

  bugfix

This command moves HEAD to point to the 'feature-1' branch, switching your working files to that branch's latest commit.

Terminal

git checkout feature-1

Expected Output

Switched to branch 'feature-1'

This command shows the latest commit where HEAD currently points, helping you confirm your current position in the project history.

Terminal

git log -1 --oneline

Expected Output

a1b2c3d Update feature-1 with new changes

→

-1 - Show only the latest commit

→

--oneline - Show commit in a short, one-line format

Key Concept

If you remember nothing else, remember: HEAD is the pointer that tells Git which commit or branch you are currently working on.

Common Mistakes

Trying to make changes without knowing which branch HEAD points to.

You might accidentally change the wrong branch or commit, causing confusion or lost work.

Always check your current branch with 'git status' or 'git branch' before making changes.

Assuming HEAD always points to a branch instead of a commit.

HEAD can point directly to a commit (detached HEAD), which means changes might be lost if not handled properly.

Understand when HEAD is detached and create a branch if you want to keep changes.

Summary

Use 'git status' or 'git branch' to see where HEAD is pointing.

HEAD points to the current branch or commit you are working on.

Switch branches with 'git checkout' to move HEAD to a different branch.

Practice

1. What does the HEAD pointer in Git represent?

easy

A. The current commit your working directory is based on

B. The remote repository URL

C. The list of all branches

D. The stash of uncommitted changes

Solution

1. Step 1: Understand the role of HEAD in Git

   HEAD points to the current commit that your working directory reflects.

2. Step 2: Differentiate HEAD from other Git concepts

   HEAD is not related to remote URLs, branch lists, or stash; it tracks your current position in history.

3. Final Answer:

   The current commit your working directory is based on -> Option A

4. Quick Check:

   HEAD = current commit [OK]

Hint: HEAD always points to your current commit position [OK]

Common Mistakes:

• Confusing HEAD with remote repository
• Thinking HEAD lists branches
• Assuming HEAD stores uncommitted changes

2. Which Git command correctly moves the HEAD pointer to the branch named feature?

easy

A. git merge feature

B. git checkout feature

C. git push feature

D. git commit feature

Solution

1. Step 1: Identify the command to switch branches

   The git checkout command moves HEAD to the specified branch.

2. Step 2: Confirm other commands do not move HEAD

   git commit creates commits, git push uploads changes, git merge combines branches but does not move HEAD directly.

3. Final Answer:

   git checkout feature -> Option B

4. Quick Check:

   Switch branch = git checkout [OK]

Hint: Use git checkout to move HEAD to another branch [OK]

Common Mistakes:

• Using git commit to switch branches
• Confusing git push with moving HEAD
• Thinking git merge moves HEAD

3. Given the following commands run in order:

git checkout main
# HEAD points to main branch

git checkout -b new-feature
# Create and switch to new-feature branch

git commit -m "Add feature"
# Commit on new-feature branch

What does HEAD point to after these commands?

medium

A. No commit, HEAD is detached

B. The latest commit on the main branch

C. The initial commit of the repository

D. The latest commit on the new-feature branch

Solution

1. Step 1: Track HEAD movement through commands

   Initially, HEAD points to main branch. Then git checkout -b new-feature creates and switches HEAD to new-feature branch.

2. Step 2: Commit on new-feature updates HEAD

   The commit adds a new commit on new-feature branch, so HEAD points to this latest commit.

3. Final Answer:

   The latest commit on the new-feature branch -> Option D

4. Quick Check:

   HEAD follows current branch's latest commit [OK]

Hint: HEAD moves with branch switch and points to latest commit [OK]

Common Mistakes:

• Assuming HEAD stays on main after branch creation
• Thinking HEAD detaches after commit
• Confusing initial commit with latest commit

4. You ran git checkout HEAD~1 but now your prompt shows (HEAD detached at ...). What is the problem?

medium

A. HEAD is detached because you checked out a commit, not a branch

B. HEAD is detached because you deleted the branch

C. HEAD is detached because the repository is corrupted

D. HEAD is detached because you pushed to remote

Solution

1. Step 1: Understand what git checkout HEAD~1 does

   This command checks out the commit before the current HEAD, not a branch.

2. Step 2: Explain detached HEAD state

   Checking out a commit directly detaches HEAD, meaning it points to a commit, not a branch.

3. Final Answer:

   HEAD is detached because you checked out a commit, not a branch -> Option A

4. Quick Check:

   Detached HEAD = checked out commit, not branch [OK]

Hint: Detached HEAD means checked out a commit, not a branch [OK]

Common Mistakes:

• Thinking detached HEAD means repo corruption
• Assuming branch was deleted
• Confusing push with HEAD detachment

5. You want to move HEAD back two commits on the current branch but keep your working files unchanged. Which command should you use?

hard

A. git reset --hard HEAD~2

B. git checkout HEAD~2

C. git reset --soft HEAD~2

D. git revert HEAD~2

Solution

1. Step 1: Understand reset options

   git reset --soft moves HEAD and branch pointer but keeps working directory unchanged.

2. Step 2: Compare other options

   --hard resets files too, checkout detaches HEAD, revert creates a new commit undoing changes.

3. Final Answer:

   git reset --soft HEAD~2 -> Option C

4. Quick Check:

   Reset soft moves HEAD, keeps files [OK]

Hint: Use git reset --soft to move HEAD without changing files [OK]

Common Mistakes:

• Using --hard and losing changes
• Using checkout and detaching HEAD
• Using revert which creates new commits