Partial clone for reduced download in Git - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to start a partial clone with filter blob:none.

Git

git clone --filter [1] https://github.com/example/repo.git

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

Aall

Btree:0

Cblob:all

Dblob:none

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'all' downloads everything, no reduction.

Using 'tree:0' filters trees, not blobs.

Using 'blob:all' downloads all blobs, no reduction.

The --filter=blob:none option tells Git to exclude blobs (file contents) during clone, reducing download size.

2fill in blank

medium

Complete the command to fetch missing blobs after a partial clone.

Git

git fetch origin [1]

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

A--filter=blob:limit=0

B--no-filter

C--filter=blob:none

D--filter=blob:deepen=1

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'blob:none' fetches no blobs.

Using 'blob:limit=0' fetches no blobs.

Using 'blob:deepen=1' is for shallow clones, not partial clones.

The --no-filter option fetches all objects including missing blobs to complete the clone.

3fill in blank

hard

Fix the error in the partial clone command to correctly specify the filter option.

Git

git clone --filter [1] https://github.com/example/repo.git

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

Ablob:none

Bblob:none --depth=1

Cfilter=blob:none

D--blob:none

Attempts:

3 left

💡 Hint

Common Mistakes

Adding extra dashes '--' before the filter value.

Including 'filter=' inside the blank.

Appending unrelated options inside the blank.

The correct syntax is --filter=blob:none. The blank replaces the value after --filter=.

4fill in blank

hard

Fill both blanks to create a partial clone and fetch missing blobs later.

Git

git clone --filter [1] https://github.com/example/repo.git && git fetch origin [2]

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

Ablob:none

B--filter=blob:none

C--no-filter

Dblob:unshallow

Attempts:

3 left

💡 Hint

Common Mistakes

Using '--filter=' in the first blank.

Using 'no-filter' without '--' in the fetch command.

Mixing up the order of filter options.

Use blob:none to exclude blobs during clone, then --no-filter to fetch missing blobs.

5fill in blank

hard

Fill all three blanks to create a partial clone, fetch missing blobs, and check the clone status.

Git

git clone --filter [1] https://github.com/example/repo.git && git fetch origin [2] && git [3]

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

Ablob:none

B--no-filter

Cstatus

Dlog

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'log' instead of 'status' for the last command.

Omitting '--' in the fetch command.

Using '--filter=' in the clone filter blank.

Clone with blob:none, fetch missing blobs with --no-filter, then check status with git status.

Practice

1. What is the main benefit of using a partial clone in Git with --filter=blob:none?

easy

A. It compresses the repository files to save disk space.

B. It clones the entire repository including all files immediately.

C. It deletes files from the repository after cloning.

D. It downloads only the repository metadata without file contents initially.

Solution

1. Step 1: Understand what --filter=blob:none does

   This option tells Git to skip downloading file contents (blobs) initially, only fetching metadata like commits and trees.

2. Step 2: Identify the benefit of skipping blobs

   By not downloading file contents, the clone is faster and uses less disk space at first, especially useful for large repos.

3. Final Answer:

   It downloads only the repository metadata without file contents initially. -> Option D

4. Quick Check:

   Partial clone with blob:none skips file contents [OK]

Hint: Partial clone skips files, downloads metadata only [OK]

Common Mistakes:

• Thinking it downloads all files immediately
• Confusing partial clone with compression
• Assuming it deletes files after clone

2. Which Git command correctly performs a partial clone that skips downloading file contents initially?

easy

A. git clone --no-checkout https://github.com/user/repo.git

B. git clone --filter=blob:none https://github.com/user/repo.git

C. git clone --shallow-since=2023-01-01 https://github.com/user/repo.git

D. git clone --depth=1 https://github.com/user/repo.git

Solution

1. Step 1: Identify the correct filter option for partial clone

   The --filter=blob:none option tells Git to skip downloading blobs (file contents) initially, enabling partial clone.

2. Step 2: Compare other options

   --depth=1 and --shallow-since create shallow clones but still download blobs. --no-checkout delays checkout but downloads all data.

3. Final Answer:

   git clone --filter=blob:none https://github.com/user/repo.git -> Option B

4. Quick Check:

   Partial clone uses --filter=blob:none [OK]

Hint: Use --filter=blob:none for partial clone [OK]

Common Mistakes:

• Using shallow clone options instead of filter
• Confusing --no-checkout with partial clone
• Omitting the filter option

3. After running git clone --filter=blob:none https://github.com/user/large-repo.git, what will happen when you try to open a file that was not downloaded yet?

medium

A. Git will automatically download the file content on demand.

B. Git will show an error that the file does not exist.

C. Git will open an empty file with no content.

D. Git will refuse to open the file until a full clone is done.

Solution

1. Step 1: Understand partial clone behavior on missing blobs

   Partial clone downloads metadata but not blobs. When a file is accessed, Git fetches the missing blob from the server automatically.

2. Step 2: Identify the user experience

   This on-demand download makes partial clone seamless, so the file opens normally after fetching content.

3. Final Answer:

   Git will automatically download the file content on demand. -> Option A

4. Quick Check:

   Partial clone fetches blobs on file access [OK]

Hint: Files download automatically when accessed in partial clone [OK]

Common Mistakes:

• Assuming files are missing or empty
• Thinking Git errors out on missing blobs
• Believing full clone is required to open files

4. You tried git clone --filter=blob:none https://github.com/user/repo.git but got an error: fatal: protocol error: bad pack header. What is the likely cause?

medium

A. The remote Git server does not support partial clone filters.

B. You typed the URL incorrectly.

C. Your local Git version is too old to support partial clone.

D. You forgot to add --depth=1 option.

Solution

1. Step 1: Understand the error context

   The error indicates the server sent unexpected data, often because it does not support the requested partial clone filter.

2. Step 2: Identify the cause

   Partial clone requires server support. If the server is old or not configured for partial clone, it rejects the filter request causing this error.

3. Final Answer:

   The remote Git server does not support partial clone filters. -> Option A

4. Quick Check:

   Server must support partial clone filters [OK]

Hint: Check server supports partial clone filters if error occurs [OK]

Common Mistakes:

• Assuming URL typo causes this error
• Thinking local Git version is always the cause
• Adding unrelated options like --depth=1

5. You want to clone a large repository but only need files in the docs/ folder initially. Which command correctly uses partial clone to reduce download size?

hard

A. git clone --filter=blob:none https://github.com/user/large-repo.git && cd large-repo && git checkout docs/

B. git clone --depth=1 https://github.com/user/large-repo.git && cd large-repo && git checkout docs/

C. git clone --filter=blob:none --filter=tree:0 --sparse https://github.com/user/large-repo.git && cd large-repo && git sparse-checkout set docs/

D. git clone --sparse https://github.com/user/large-repo.git && cd large-repo && git sparse-checkout set docs/

Solution

1. Step 1: Combine partial clone and sparse checkout

   Partial clone with --filter=blob:none --filter=tree:0 reduces blobs and trees downloaded. Adding --sparse enables sparse checkout mode.

2. Step 2: Set sparse checkout to only docs/

   After cloning, running git sparse-checkout set docs/ fetches only the docs/ folder content on demand.

3. Final Answer:

   git clone --filter=blob:none --filter=tree:0 --sparse https://github.com/user/large-repo.git && cd large-repo && git sparse-checkout set docs/ -> Option C

4. Quick Check:

   Partial clone + sparse checkout limits download to docs/ [OK]

Hint: Use --filter=blob:none --filter=tree:0 with --sparse and sparse-checkout [OK]

Common Mistakes:

• Using shallow clone instead of partial clone
• Not enabling sparse checkout with --sparse
• Trying to checkout folder without sparse mode