How branches are just files with hashes in Git - Practice Exercises

Challenge - 5 Problems

🧠 Conceptual

intermediate

What does a Git branch file contain?

In Git, branches are stored as files inside the .git/refs/heads/ directory. What is the content of these branch files?

A The full commit history of the branch as text

B A list of all files changed in the branch

C The branch name repeated multiple times

D The SHA-1 hash of the latest commit the branch points to

💡 Hint

Think about what uniquely identifies a commit in Git.

Each branch file contains the SHA-1 hash of the latest commit it points to. This hash lets Git know the current state of the branch.

💻 Command Output

intermediate

Reading a branch file content

You run the command cat .git/refs/heads/main in your Git repository. What output do you expect?

A The SHA-1 hash of the latest commit on main

B A list of all commits on the main branch

C The branch name 'main'

D An error saying the file does not exist

💡 Hint

Try to remember what the branch file stores inside the .git folder.

The branch file contains the SHA-1 hash of the latest commit on that branch, so cat shows that hash.

❓ Troubleshoot

advanced

Why does Git say 'fatal: not a git repository' when reading a branch file?

You try to run git rev-parse refs/heads/feature but get the error fatal: not a git repository. What is the most likely cause?

A You are not inside a Git repository directory

B The branch name 'feature' does not exist

C The branch file is corrupted and unreadable

D Your Git version is outdated

💡 Hint

Check your current folder and if it contains a .git directory.

This error usually means you are running the command outside a Git repository folder, so Git cannot find the .git directory.

🔀 Workflow

advanced

How to update a branch pointer manually

You want to manually update the dev branch to point to a specific commit hash abc1234. Which command correctly updates the branch file?

A echo abc1234 > .git/refs/heads/dev

B git update-ref refs/heads/dev abc1234

C git branch dev abc1234

D git checkout dev && git reset --hard abc1234

💡 Hint

Think about the safest Git command to update branch references.

The git update-ref command safely updates the branch pointer to the given commit hash without changing the working directory.

✅ Best Practice

expert

Why should you avoid manually editing branch files?

Branch files in Git are simple text files containing commit hashes. Why is it recommended to avoid manually editing these files?

A Git automatically overwrites manual changes on next commit

B Manual edits are faster but less secure than Git commands

C Manual edits can cause Git to lose track of commits and corrupt the repository

D Manual edits are required only for advanced users

💡 Hint

Consider what happens if the branch points to a non-existent commit hash.

Editing branch files manually risks pointing branches to invalid commits, which can corrupt the repository and cause data loss.

Practice

1. What does a Git branch file store internally?

easy

A. A commit hash pointing to a specific commit

B. The entire project files

C. The list of all branches

D. The commit message text

Solution

1. Step 1: Understand what a branch represents

   A branch in Git is a pointer to a commit, not the files themselves.

2. Step 2: Identify what is stored in the branch file

   The branch file stores the commit hash it points to, which identifies the commit.

3. Final Answer:

   A commit hash pointing to a specific commit -> Option A

4. Quick Check:

   Branch file = commit hash [OK]

Hint: Branches store commit hashes, not files or messages [OK]

Common Mistakes:

• Thinking branches store full project files
• Confusing branch files with commit messages
• Assuming branches list all other branches

2. Which command shows the content of the branch file for main in Git?

easy

A. git show main

B. cat .git/refs/heads/main

C. git branch main

D. git log main

Solution

1. Step 1: Locate branch files in Git directory

   Branch files are stored in .git/refs/heads/ folder.

2. Step 2: Use a command to read the branch file content

   The cat command reads the file content, showing the commit hash.

3. Final Answer:

   cat .git/refs/heads/main -> Option B

4. Quick Check:

   Read branch file with cat [OK]

Hint: Branch files are plain files under .git/refs/heads/ [OK]

Common Mistakes:

• Using git show which shows commit details, not raw hash
• Using git branch which lists branches, not file content
• Using git log which shows commit history, not branch file

3. Given the branch file .git/refs/heads/feature contains abc1234, what does git checkout feature do?

medium

A. Creates a new commit with hash abc1234

B. Deletes the feature branch

C. Moves HEAD to commit abc1234 and updates working files

D. Shows the commit message of abc1234

Solution

1. Step 1: Understand what git checkout does with a branch

   It moves the HEAD pointer to the commit the branch points to.

2. Step 2: Connect branch file content to checkout effect

   The branch file has commit hash abc1234, so checkout moves HEAD there and updates files.

3. Final Answer:

   Moves HEAD to commit abc1234 and updates working files -> Option C

4. Quick Check:

   Checkout moves HEAD to branch commit [OK]

Hint: Checkout moves HEAD to branch's commit hash [OK]

Common Mistakes:

• Thinking checkout deletes branches
• Confusing checkout with commit creation
• Assuming checkout only shows commit messages

4. You see that .git/refs/heads/dev file is empty. What problem will this cause?

medium

A. Git will ignore the dev branch and use main instead

B. Git will create a new commit automatically

C. Git will treat dev as a remote branch

D. Git cannot find the commit for branch dev, causing errors on checkout

Solution

1. Step 1: Understand branch file role in Git

   The branch file must contain a commit hash to point to a commit.

2. Step 2: Analyze effect of empty branch file

   If empty, Git cannot find the commit, so checkout or other commands fail with errors.

3. Final Answer:

   Git cannot find the commit for branch dev, causing errors on checkout -> Option D

4. Quick Check:

   Empty branch file breaks commit reference [OK]

Hint: Branch files must have commit hashes, never be empty [OK]

Common Mistakes:

• Assuming Git auto-fixes empty branch files
• Confusing empty branch file with remote branch
• Thinking Git defaults to main silently

5. You want to create a new branch release pointing to the same commit as main. Which command correctly updates the branch file?

hard

A. git checkout -b release main

B. git branch release main

C. A and B

D. echo $(cat .git/refs/heads/main) > .git/refs/heads/release

Solution

1. Step 1: Understand how branches point to commits

   Branches are files storing commit hashes. Copying main's hash creates release at same commit.

2. Step 2: Analyze each option's effect

   echo $(cat .git/refs/heads/main) > .git/refs/heads/release manually copies the hash file content. git branch release main creates branch release at main's commit. git checkout -b release main creates and switches to release at main's commit.

3. Step 3: Confirm which options update branch file correctly

   Options A, B, and D all create the release branch pointing to main's commit, but only D is a single command that creates and switches to the branch.

4. Final Answer:

   git checkout -b release main -> Option A

5. Quick Check:

   git checkout -b creates and switches branch [OK]

Hint: Multiple ways to set branch file to same commit hash, but checkout -b is most common [OK]

Common Mistakes:

• Thinking only git commands can create branches
• Ignoring manual file editing possibility
• Confusing checkout with branch creation only