Garbage collection with git gc - Step-by-Step Execution

Process Flow - Garbage collection with git gc

Start: git repository

↓

Run git gc command

↓

Scan objects in .git/objects

↓

Identify unreachable objects

↓

Compress reachable objects

↓

Remove unreachable objects

↓

Update repository state

↓

Finish: optimized repository

The git gc command scans the repository, compresses reachable objects, removes unreachable ones, and updates the repository to optimize storage.

Execution Sample

Git

git gc
# Runs garbage collection to clean and optimize the repo

This command cleans up unnecessary files and optimizes the local git repository.

Process Table

Step	Action	Details	Result
1	Start git gc	Begin garbage collection process	Ready to scan objects
2	Scan objects	Look through .git/objects folder	List of all objects found
3	Identify unreachable objects	Find objects not referenced by any branch, tag, or stash	Unreachable objects marked for removal
4	Compress reachable objects	Pack loose objects into packfiles	Storage optimized
5	Remove unreachable objects	Delete objects no longer needed	Disk space freed
6	Update repository state	Update refs and packfiles	Repository optimized
7	Finish	Garbage collection complete	Repository ready for use

💡 All unreachable objects removed and reachable objects compressed, git gc process ends

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
Objects in repo	All objects (loose + packed)	All objects listed	Reachable + unreachable identified	Reachable compressed	Unreachable removed	Optimized set of objects

Key Moments - 2 Insights

Why does git gc remove some objects but not others?

git gc only removes unreachable objects, which are not referenced by any branch, tag, or stash. Reachable objects are kept and compressed for efficiency, as shown in steps 3 and 5 of the execution table.

What does compressing objects mean in git gc?

Compressing means packing many small loose objects into fewer packfiles to save space and improve performance. This happens in step 4, reducing storage size without losing data.

Visual Quiz - 3 Questions

Look at the execution table, at which step are unreachable objects removed?

A Step 4

B Step 5

C Step 3

D Step 6

💡 Hint

Check the 'Action' column for removal of unreachable objects in the execution table.

According to the variable tracker, what happens to the objects after step 4?

A All objects are removed

B Unreachable objects are listed

C Reachable objects are compressed

D Repository state is updated

💡 Hint

Look at the 'After Step 4' column in the variable tracker for objects in repo.

If no unreachable objects exist, which step would have no effect?

A Step 5

B Step 3

C Step 4

D Step 6

💡 Hint

Refer to the execution table where unreachable objects are removed.

Concept Snapshot

git gc runs garbage collection in a git repo
It scans all objects and identifies unreachable ones
Unreachable objects are deleted to free space
Reachable objects are compressed into packfiles
This optimizes storage and speeds up git operations

Full Transcript

The git gc command starts by scanning all objects in the repository's .git/objects folder. It identifies which objects are reachable, meaning they are referenced by branches, tags, or stashes, and which are unreachable. Unreachable objects are those no longer needed and safe to remove. Then, git gc compresses the reachable objects by packing them into fewer files to save space. After removing unreachable objects and compressing reachable ones, git gc updates the repository state to reflect these changes. This process frees disk space and improves repository performance. The execution table shows each step clearly, and the variable tracker follows how the objects change during the process.