What git commit Actually Creates (it's not your changes)
You type git commit and a save point appears instantly — but what actually got created? Here's how Git really works under the hood: a content-addressed graph of immutable snapshots, not a record of your changes.
In this video:
• The three objects: blobs, trees, and commits — all named by a hash of their contents
• Why Git stores whole snapshots, not diffs (and why that's not wasteful)
• How a branch is just a 40-character pointer, and what HEAD really is
• What commit, branch, merge, checkout and reset do to the graph
• Why Git is tamper-evident — a chain of fingerprints, years before blockchains
⏱ Chapters
0:00 What git commit creates
0:53 Blobs: content-addressed
1:18 Trees: directory snapshots
1:44 Commits
2:08 The three trees (staging)
2:59 Snapshots, not diffs
3:52 It's just files on disk
4:40 Branches & HEAD
5:28 Detached HEAD
5:55 Commit, branch, merge
7:58 Tamper-evident
10:04 Recap
🎬 Series: Under the Hood
🔔 Subscribe to Bracen — computer science, made to click. One idea, fully, every week.
▸ Instagram: @bracencs · TikTok: @bracencs · X: @bracencs · YouTube: @bracencs
✉ [email protected]
Written, animated & coded at Bracen.
#git #programming #computerscience