Garbage collection with git gc - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to run garbage collection in Git.

Git

git [1]

Drag options to blanks, or click blank then click option'

Acommit

Bclone

Cgc

Dpush

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'commit' instead of 'gc' will create a commit, not clean up files.

Using 'push' sends changes to a remote, not garbage collection.

Using 'clone' copies a repository, not related to garbage collection.

The git gc command runs garbage collection to clean up unnecessary files and optimize the local repository.

2fill in blank

medium

Complete the command to run garbage collection with aggressive optimization.

Git

git gc --[1]

Drag options to blanks, or click blank then click option'

Afast

Baggressive

Cquiet

Dverbose

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'fast' does not exist as an option for git gc.

Using 'quiet' suppresses output but does not affect optimization level.

Using 'verbose' increases output detail but not optimization.

The --aggressive option makes git gc spend extra time optimizing the repository for better compression.

3fill in blank

hard

Fix the error in the command to prune unreachable objects during garbage collection.

Git

git gc --prune=[1]

Drag options to blanks, or click blank then click option'

Anow

Bnever

Calways

Dlater

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'never' means no pruning happens.

Using 'always' is not a valid prune option.

Using 'later' is not recognized by git gc.

The --prune=now option tells Git to remove unreachable objects immediately during garbage collection.

4fill in blank

hard

Fill both blanks to run garbage collection quietly and prune objects older than 2 weeks.

Git

git gc --[1] --prune=[2]

Drag options to blanks, or click blank then click option'

Aquiet

Bnow

C2.weeks.ago

Dverbose

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'verbose' instead of 'quiet' will increase output.

Using 'now' prunes immediately, not older than 2 weeks.

Mixing options incorrectly can cause errors.

The --quiet option suppresses output, and --prune=2.weeks.ago removes unreachable objects older than two weeks.

5fill in blank

hard

Fill all three blanks to run aggressive garbage collection, prune immediately, and show verbose output.

Git

git gc --[1] --prune=[2] --[3]

Drag options to blanks, or click blank then click option'

Aaggressive

Bnow

Cverbose

Dquiet

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'quiet' instead of 'verbose' hides output.

Using 'later' or invalid prune values causes errors.

Omitting aggressive makes optimization less thorough.

This command runs garbage collection aggressively, prunes unreachable objects immediately, and shows detailed output.

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