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.