Git HEAD Explained: How Commits Create a Single Snapshot Across Multiple Files | Git Internals
Understand how Git really works under the hood by learning what HEAD actually represents and why Git tracks snapshots of the entire repository, not individual file histories.
In this lesson, I walk through a hands-on Git lab where:
One file is committed multiple times
A second file is added later
Both files have uneven commit histories
Yet HEAD correctly reflects the latest combined snapshot
You’ll clearly see:
Why HEAD is not “the latest commit of a file”
How the staging area (index) determines what gets committed
How files added later inherit the current project state
Why Git history is repository-centric, not file-centric
🧠 What You’ll Learn
How Git commits form a single timeline per repository
The difference between working directory, staging area, and HEAD
How git show HEAD:file works
Why every Git commit is a complete snapshot
How to reason about file states during interviews and debugging
🧪 Commands Used
git init
git add
git commit
git ls-files
git show :file
git show HEAD:file
🎯 Who This Lesson Is For
Beginners learning Git fundamentals
Developers preparing for Git interview questions
Students who want to understand Git beyond commands
Anyone confused about HEAD, staging, and commit history
💡 Key Takeaway
Git does not track files independently — it tracks complete project snapshots, and HEAD always points to the latest one.
👉 Like, Share, and Subscribe for more deep-dive Git, Linux, and Networking lessons.