Partial clone for reduced download in Git - Commands & Configuration

Introduction

Sometimes repositories are very large, and downloading everything takes a lot of time and space. Partial clone lets you download only the parts you need right now, saving time and disk space.

When you want to start working on a large project quickly without waiting for the full repository download.

When your internet connection is slow or has data limits and you want to save bandwidth.

When you only need specific parts of a repository, like a single folder or file, not the entire history.

When working on a shared project where many large files are rarely changed and can be fetched on demand.

When using continuous integration systems that only need parts of the code to run tests.

Commands

This command clones the Git repository but skips downloading file contents (blobs) initially, only fetching metadata and commit history.

Terminal

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

Expected Output

Cloning into 'git'...

remote: Enumerating objects: 100000, done.

remote: Counting objects: 100% (100000/100000), done.

remote: Compressing objects: 100% (50000/50000), done.

Receiving objects: 100% (100000/100000), 20.00 MiB | 2.00 MiB/s, done.

Resolving deltas: 100% (50000/50000), done.

→

--filter=blob:none - Avoid downloading file contents initially to reduce data transfer.

Change directory into the cloned repository to start working inside it.

Terminal

cd git

Expected Output

No output (command runs silently)

Initialize sparse checkout in cone mode to allow checking out only specific folders or files.

Terminal

git sparse-checkout init --cone

Expected Output

Sparse checkout initialized.

→

--cone - Simplifies sparse checkout to work with folder patterns.

Configure sparse checkout to only include the 'Documentation' folder in the working directory.

Terminal

git sparse-checkout set Documentation

Expected Output

Updated working directory.

Checkout the main branch, downloading file contents only for the sparse paths set.

Terminal

git checkout main

Expected Output

Switched to branch 'main'

Downloading objects: 100% (500/500), 5.00 MiB | 1.00 MiB/s, done.

Key Concept

If you remember nothing else from this pattern, remember: partial clone downloads only metadata first and fetches file contents on demand to save time and space.

Common Mistakes

Running git clone without the --filter=blob:none flag for large repos.

This downloads the entire repository including all file contents, causing slow clone and large disk use.

Always add --filter=blob:none to clone only metadata initially for large repositories.

Not initializing sparse checkout before setting sparse paths.

Git will not apply sparse checkout rules and will check out the full repository.

Run git sparse-checkout init --cone before setting sparse paths.

Trying to access files not included in sparse checkout paths.

Those files are not downloaded or checked out, so they appear missing.

Add needed folders or files to sparse checkout with git sparse-checkout set.

Summary

Use git clone --filter=blob:none to clone only metadata and reduce download size.

Initialize sparse checkout with git sparse-checkout init --cone to control which parts of the repo to check out.

Set specific folders or files to check out with git sparse-checkout set and then checkout the branch.

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