Garbage collection with git gc - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the git gc command?

git gc stands for garbage collection. It cleans up unnecessary files and optimizes the local repository to save space and improve performance.

intermediate

Which files does git gc typically remove or compress?

It removes unreachable objects (like old commits no longer referenced) and compresses loose objects into pack files to reduce disk space.

intermediate

When does Git automatically run garbage collection?

Git runs garbage collection automatically after a certain number of changes or when the repository reaches a size threshold.

beginner

How can you force Git to run garbage collection manually?

By running the command git gc in your repository folder.

beginner

What is a pack file in Git?

A pack file is a compressed collection of Git objects that saves space and speeds up repository operations.

What does git gc do?

A Creates a new commit

B Deletes all branches

C Cleans up and optimizes the repository

D Clones a repository

git gc cleans up unnecessary files and optimizes the repository.

Which of these is NOT a result of running git gc?

A Deleting the entire repository

B Removing unreachable objects

C Compressing loose objects

D Creating pack files

git gc does not delete the entire repository.

When does Git automatically run garbage collection?

A After every commit

B When you push to remote

C Only when you run <code>git gc</code> manually

D When repository size or changes reach a threshold

Git runs garbage collection automatically when certain thresholds are met.

What is a pack file in Git?

A A backup of your repository

B A compressed file storing multiple Git objects

C A branch name

D A commit message

A pack file compresses multiple Git objects to save space.

How do you manually trigger garbage collection in Git?

A git gc

B git prune

C git clean

D git reset

Use git gc to manually run garbage collection.

Explain what happens when you run git gc in your repository.

Think about cleaning and organizing your repository files.

Describe when and why Git runs garbage collection automatically.

Git helps keep your repo tidy behind the scenes.

Practice

1. What is the main purpose of the git gc command?

easy

A. To create a new branch in the repository

B. To clean up unnecessary files and optimize the repository

C. To clone a remote repository locally

D. To merge two branches together

Solution

1. Step 1: Understand the function of git gc

   The git gc command stands for garbage collection and is used to clean up unnecessary files in a Git repository.

2. Step 2: Identify the main effect of running git gc

   Running git gc reduces repository size and improves performance by removing unneeded files.

3. Final Answer:

   To clean up unnecessary files and optimize the repository -> Option B

4. Quick Check:

   Garbage collection = Clean up files [OK]

Hint: Remember: gc means garbage collection, cleans repo files [OK]

Common Mistakes:

• Confusing git gc with branch creation
• Thinking it clones repositories
• Assuming it merges branches

2. Which of the following is the correct syntax to run an aggressive garbage collection in Git?

easy

A. git gc --aggressive

B. git gc --fast

C. git gc -a

D. git gc --deep-clean

Solution

1. Step 1: Recall the option for deeper cleanup

   The --aggressive option tells Git to perform a more thorough garbage collection.

2. Step 2: Match the correct syntax

   The correct command is git gc --aggressive. Other options like --fast or --deep-clean do not exist.

3. Final Answer:

   git gc --aggressive -> Option A

4. Quick Check:

   Deeper cleanup = --aggressive [OK]

Hint: Use --aggressive for deep cleanup, not --fast [OK]

Common Mistakes:

• Using non-existent flags like --deep-clean
• Confusing -a with --aggressive
• Assuming --fast does deep cleanup

3. What will be the effect of running git gc on a repository with many unreachable objects?

medium

A. It will reset the repository to the last commit

B. It will create new unreachable objects

C. It will delete unreachable objects and compress repository data

D. It will only update branch pointers

Solution

1. Step 1: Understand unreachable objects in Git

   Unreachable objects are files or commits not referenced by any branch or tag and can be safely removed.

2. Step 2: Effect of git gc on unreachable objects

   Running git gc deletes these unreachable objects and compresses data to optimize the repository.

3. Final Answer:

   It will delete unreachable objects and compress repository data -> Option C

4. Quick Check:

   Garbage collection removes unreachable objects [OK]

Hint: Garbage collection removes unneeded data safely [OK]

Common Mistakes:

• Thinking it creates unreachable objects
• Confusing it with reset commands
• Assuming it only updates pointers

4. You ran git gc --aggressive but noticed the repository size did not reduce much. What could be a possible reason?

medium

A. Git does not support aggressive garbage collection

B. The command syntax was incorrect

C. The repository is corrupted

D. There are many recent commits and few unreachable objects

Solution

1. Step 1: Understand when garbage collection reduces size

   Garbage collection mainly removes unreachable objects and compresses data. If most data is reachable, size won't reduce much.

2. Step 2: Analyze the scenario

   If the repository has many recent commits and few unreachable objects, git gc --aggressive will have little effect on size.

3. Final Answer:

   There are many recent commits and few unreachable objects -> Option D

4. Quick Check:

   Few unreachable objects = little size change [OK]

Hint: Aggressive gc helps only if unreachable objects exist [OK]

Common Mistakes:

• Assuming syntax error without checking
• Believing aggressive gc is unsupported
• Jumping to repository corruption conclusion

5. You want to reduce your Git repository size significantly and improve performance. Which sequence of commands should you run?

hard

A. git gc --aggressive; git prune; git gc

B. git gc; git gc --aggressive; git prune

C. git prune; git gc --aggressive; git gc

D. git fetch; git gc --aggressive; git prune

Solution

1. Step 1: Understand the role of each command

   git gc --aggressive performs deep cleanup, git prune removes unreachable objects, and running git gc again optimizes after pruning.

2. Step 2: Determine the best order

   First run git gc --aggressive for deep cleanup, then git prune to remove unreachable objects, and finally git gc to optimize the repository fully.

3. Final Answer:

   git gc --aggressive; git prune; git gc -> Option A

4. Quick Check:

   Deep cleanup + prune + optimize = D [OK]

Hint: Run aggressive gc, then prune, then gc again for best cleanup [OK]

Common Mistakes:

• Running prune before aggressive gc
• Skipping final gc optimization
• Confusing fetch with garbage collection