Git internals: Why trees are a developer's best friend
summary
Covers how Git stores snapshots as blobs, trees and commits, how the index and reflogs for recovery work, and the real effects of commands: checkout recursively rebuilds the top-level tree, reset --hard just moves the branch pointer and discards working changes, reset --soft keeps them, cherry-pick reapplies a commit with a new parent, rebase replays diffs and rewrites hashes. Describes storage optimizations: two-character subdirectories for objects, packfiles with deltas produced by git gc and push, and the risk of SHA-1 collisions.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:48Key Directories
- 6:29Commit objects
- 9:51Blobs
- 13:42Branches
- 18:59Remotes
- 22:31Bonus - optimization
- 32:09git merge
- 35:59git rebase
