Git work like saving system for code. It save code again and again. Git not save only file but save whole project state. Every time we save Git make new copy. Old copy never delete. This help go back anytime.

Code → Save → Save → History

What is the .git Folder

.git folder is very important. Git keep all brain inside it. When we do git init this folder come. Inside .git Git keep data about code. If .git delete Git stop working. We should never change this folder.

Project → .git → Git Data

Inside the .git Folder Inside .git many things are there. Objects folder store code data. Head tell which branch is active. Refs store branch names. Config store setting. All magic happen here.

.git → objects → refs → HEAD → config

What are Git Objects

Git save data in objects. Git only understand objects. There are three main objects blob tree commit. These objects connect with each other. Git use this to track project.

Blob → Tree → Commit

Blob Object Explained

Blob store file content only. It not know file name. It not know folder. It only know data inside file. Same data mean same blob. This save memory.

File Data → Blob

Tree Object Explained Tree object store folder info. It connect file name to blob. It also connect folder to other tree. Tree show project structure.

Folder → Tree → Files Commit Object

Explained

Commit object is final thing. Commit point to tree. Commit also point to old commit. Commit have message and time. This make history. Commit → Tree → Old Commit

How Git Track Changes

Git not change old file. When file change Git make new blob. New tree created. New commit created. Old data still there. Git never forget.

Old Data → New Data → New Commit

What Happen in git add

git add mean prepare file. When we do git add Git create blob. Blob go inside .git folder. File now ready to save.

File → git add → Blob What Happen in git commit

git commit mean save work. Git create commit object. It link commit to tree. Tree link to blobs. Commit stay forever. Blobs → Tree → Commit

How Git Use Hash

Git use hash to name data. Hash is long number and letter. Same file same hash. Change file change hash. This keep data safe.

Data → Hash → Stored Why Learn Git Internals If we know Git inside working we not fear Git. We understand why command work. We not blindly type command. This make us better developer.

Understanding → Confidence → Growth Simple Git Mental Model

Think Git like box of objects. Files become blobs. Folders become trees. Commits connect all. Git just manage objects.

Files → Blobs → Trees → Commits