How branches are just files with hashes in Git - Quick Revision & Summary

Recall & Review

beginner

What is a Git branch in simple terms?

A Git branch is just a file that stores the hash (a unique ID) of the latest commit on that branch.

beginner

How does Git know which commit a branch points to?

Git reads the branch file which contains the hash of the commit it points to. This hash tells Git the exact snapshot of the project.

intermediate

What happens to the branch file when you make a new commit?

The branch file updates to store the new commit's hash, so the branch always points to the latest commit.

intermediate

Where are branch files stored in a Git repository?

Branch files are stored inside the .git/refs/heads directory as simple text files containing commit hashes.

beginner

Why is it useful to think of branches as files with hashes?

Because it shows branches are lightweight pointers to commits, making Git fast and efficient at switching and managing code versions.

What does a Git branch file contain?

A The list of all commits in the branch

B The full source code of the project

C The commit message of the last commit

D The hash of the latest commit on that branch

A Git branch file stores the hash of the latest commit it points to, not the full code or commit messages.

Where can you find branch files inside a Git repository?

A .git/objects/

B .git/config

C .git/refs/heads/

D .git/hooks/

Branch files are stored as simple files inside the .git/refs/heads directory.

What happens to a branch file when you commit new changes?

A It updates to the new commit's hash

B It deletes the old commit

C It creates a new branch file

D It stores the commit message

The branch file updates to point to the new commit hash after a commit.

Why are branches considered lightweight in Git?

A Because they are stored in the cloud

B Because they are just files with commit hashes

C Because they contain all commit messages

D Because they store full copies of the project

Branches are lightweight because they only store a pointer (hash) to a commit, not full project copies.

What does the commit hash in a branch file represent?

A A unique ID for a specific project snapshot

B The name of the branch

C The date of the last commit

D The author of the commit

The commit hash uniquely identifies a specific snapshot of the project at that commit.

Explain how Git branches work as files with hashes.

Think about how a branch points to a commit using a simple file.

Describe where branch files are stored and what they contain in a Git repository.

Look inside the .git folder to find branch files.