Garbage collection with git gc - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What does git gc do?

Which of the following best describes the purpose of the git gc command?

A It clones a remote repository to your local machine.

B It deletes all branches except the current one.

C It resets the repository to the last commit, discarding all changes.

D It cleans up unnecessary files and optimizes the local repository by compressing objects.

💡 Hint

Think about how Git manages storage and what cleanup might mean.

The git gc command stands for garbage collection. It removes unnecessary files and compresses objects to optimize the repository's storage.

❓ query_result

intermediate

Output of git gc --dry-run

What is the expected output when running git gc --dry-run in a repository?

A Shows the current branch name only.

B Deletes all untracked files immediately.

C Lists the files and objects that would be cleaned or compressed without making changes.

D Displays an error saying the command is invalid.

💡 Hint

The --dry-run option usually means no changes are made.

The --dry-run option simulates the garbage collection process and lists what would be done without changing anything.

📝 Syntax

advanced

Identify the correct git gc command to aggressively optimize

Which command runs git gc with aggressive optimization to compress objects more thoroughly?

A git gc --aggressive

B git gc --force-aggressive

C git gc --deep-clean

D git gc --compress-all

💡 Hint

Look for the official flag that increases compression effort.

The --aggressive flag tells git gc to spend more time compressing objects for better optimization.

🔧 Debug

advanced

Why does git gc fail with 'unable to create temporary file' error?

You run git gc and get the error: unable to create temporary file. What is the most likely cause?

A The disk is full or the user lacks write permissions in the repository directory.

B The repository has no commits yet.

C The remote repository is unreachable.

D The current branch is not checked out.

💡 Hint

Temporary files need space and permission to be created.

This error usually means Git cannot write temporary files because the disk is full or permissions are missing.

❓ optimization

expert

How to automate git gc for large repositories?

For a large repository with many objects, which approach best automates running git gc without impacting developer workflow?

A Run <code>git gc --aggressive</code> manually every time a commit is made.

B Schedule <code>git gc --auto</code> to run periodically in the background during low activity times.

C Disable garbage collection entirely to avoid any delays.

D Run <code>git gc</code> only after pushing to the remote repository.

💡 Hint

Think about balancing optimization and developer experience.

Using git gc --auto scheduled during low activity times automates cleanup without slowing down developers.

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