Git does not save the entire file every time. Git stores file data in the form of objects.

Internally, Git works on the following concepts:

Content-based tracking (the content of the file

Snapshot system (each commit is a snapshot)

Use of hashes (SHA-1 / SHA-256)

Git assigns a unique hash ID to every change.

Understanding the .git Folder

The .git folder is the brain of your project. It stores all the information, history, and settings related to your project that Git (a version control system) needs. When you run the git init command, this folder is created.

This folder is usually hidden, and it keeps a record of every change made to your code. Because of this, you can go back to any previous version at any time and see who made which changes.

It stores the following:

Commit history

Branches

Configuration

Git objects (blob, tree, commit)

HEAD pointer

If the .git folder is deleted
your entire Git history will be lost.

Git Objects: Blob, Tree, and Commit

Git stores data in the form of objects:

1. Blob (Binary Large Object)

Stores the content of files.

2. Tree

   Manages the project’s directory tree and links to blobs and other trees.

   3. Commit

   A commit is a snapshot, which contains:

• Author

• Date & Time

• Message

• Parent commit

• Reference to the tree object

The complete state of the project at that point in time.

How Git Tracks Changes

There are 3 main stages in Git:

1. Working Directory

• Where you edit files

2. Staging Area

• Files go here using git add

• They are prepared for commit

3. Repository

• After git commit, files are permanently saved here