HEAD pointer concept in Git - Mini Project: Build & Apply

Understanding the HEAD Pointer in Git

📖 Scenario: You are working on a simple Git repository to track changes in your project files. Understanding how Git's HEAD pointer works will help you manage branches and commits effectively.

🎯 Goal: Learn how to check the current HEAD pointer, create a new branch, switch branches, and observe how HEAD changes in Git.

📋 What You'll Learn

Initialize a Git repository

Create and commit a file

Check the current HEAD pointer

Create and switch to a new branch

Observe HEAD pointer changes

💡 Why This Matters

🌍 Real World

Understanding the HEAD pointer helps you manage branches and commits in real projects, avoiding mistakes like committing to the wrong branch.

💼 Career

Git is essential for developers and DevOps engineers. Knowing how HEAD works is fundamental for version control and collaboration.

1

Initialize Git repository and create first commit

Initialize a Git repository in the current folder using git init. Then create a file named file.txt with the content Hello Git. Add the file to staging using git add file.txt and commit it with the message Initial commit using git commit -m "Initial commit".

Git

# Initialize Git repository and create first commit
# Your code here

Hint

Use git init to start a new repository. Use echo to create the file content. Then add and commit the file.

2

Check the current HEAD pointer

Use the command git symbolic-ref HEAD to display the current branch that HEAD points to.

Git

git init

echo "Hello Git" > file.txt

git add file.txt

git commit -m "Initial commit"

# Use git symbolic-ref HEAD to show current HEAD pointer
# Your code here

Hint

The git symbolic-ref HEAD command shows which branch HEAD points to.

3

Create and switch to a new branch

Create a new branch named feature using git branch feature. Then switch to the feature branch using git checkout feature.

Git

git init

echo "Hello Git" > file.txt

git add file.txt

git commit -m "Initial commit"

git symbolic-ref HEAD

# Create branch 'feature' and switch to it
# Your code here

Hint

Use git branch feature to create the branch and git checkout feature to switch to it.

4

Verify HEAD pointer after switching branch

Run git symbolic-ref HEAD again to verify that HEAD now points to the feature branch.

Git

git init

echo "Hello Git" > file.txt

git add file.txt

git commit -m "Initial commit"

git symbolic-ref HEAD

git branch feature

git checkout feature

# Check HEAD pointer again
# Your code here

Hint

After switching branches, git symbolic-ref HEAD should show refs/heads/feature.

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