Sparse checkout for partial repos in Git - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is sparse checkout in Git?

Sparse checkout allows you to check out only a part of a Git repository instead of the whole repo. This saves space and time when you only need specific folders or files.

beginner

Which Git command enables sparse checkout mode?

The command git sparse-checkout init enables sparse checkout mode in your local repository.

beginner

How do you specify which folders or files to include in a sparse checkout?

You use git sparse-checkout set <folder1> <folder2> to list the folders or files you want to check out.

beginner

What is the benefit of using sparse checkout in large repositories?

Sparse checkout reduces disk space usage and speeds up operations by only downloading and checking out the parts of the repo you need.

intermediate

What is the sequence of commands to start sparse checkout on an existing Git repo?

1. git sparse-checkout init
2. git sparse-checkout set <paths>
3. git checkout <branch> (if needed to update working tree)

Which command initializes sparse checkout in Git?

A git clone --sparse

B git checkout sparse

C git sparse-checkout init

D git config sparseCheckout true

The command git sparse-checkout init enables sparse checkout mode.

How do you specify folders to include in sparse checkout?

A git sparse-checkout set <folders>

B git add <folders>

C git checkout <folders>

D git clone --filter=<folders>

Use git sparse-checkout set followed by folder names to specify what to check out.

What is a main advantage of sparse checkout?

A Faster cloning of entire repo

B Checking out only needed parts of repo

C Automatically merging branches

D Encrypting repository data

Sparse checkout lets you check out only parts of the repo you need, saving space and time.

Which file does Git use internally to track sparse checkout paths?

A .git/info/sparse-checkout

B .gitignore

C .gitattributes

D .git/config

Git stores sparse checkout paths in the file .git/info/sparse-checkout.

If you want to add more folders to sparse checkout later, what do you do?

A Edit .gitignore file

B Run git add <new folders>

C Run git clone again

D Run git sparse-checkout set with all desired folders again

You update the sparse checkout list by running git sparse-checkout set with all folders you want included.

Explain how to set up sparse checkout in an existing Git repository step-by-step.

Think about enabling sparse mode, choosing folders, and updating working tree.

Describe the benefits of using sparse checkout when working with large repositories.

Consider what happens when you don't need the whole repo.

Practice

1. What is the main purpose of using git sparse-checkout?

easy

A. To merge two branches automatically

B. To clone a repository faster by skipping all files

C. To delete files from the repository permanently

D. To download only specific parts of a repository you need

Solution

1. Step 1: Understand sparse checkout concept

   Sparse checkout allows you to work with only parts of a repo instead of the whole repo.

2. Step 2: Identify the main purpose

   This helps save space and time by downloading only needed folders or files.

3. Final Answer:

   To download only specific parts of a repository you need -> Option D

4. Quick Check:

   Sparse checkout = partial repo download [OK]

Hint: Sparse checkout means partial repo download only [OK]

Common Mistakes:

• Thinking it deletes files from the repo
• Confusing with branch merging
• Assuming it skips all files

2. Which command correctly initializes sparse checkout with cone mode?

easy

A. git sparse-checkout start --cone

B. git sparse-checkout init --cone

C. git sparse-checkout enable --cone

D. git sparse-checkout create --cone

Solution

1. Step 1: Recall the correct initialization command

   The official command to start sparse checkout in cone mode is git sparse-checkout init --cone.

2. Step 2: Verify other options

   Other commands like start, enable, or create are not valid git sparse-checkout commands.

3. Final Answer:

   git sparse-checkout init --cone -> Option B

4. Quick Check:

   Init with --cone = git sparse-checkout init --cone [OK]

Hint: Use 'init' with '--cone' to start sparse checkout [OK]

Common Mistakes:

• Using 'start' instead of 'init'
• Forgetting the '--cone' flag
• Using invalid verbs like 'enable' or 'create'

3. After running git sparse-checkout set docs src, which folders will be present in your working directory?

medium

A. No folders, only files at root

B. All folders except 'docs' and 'src'

C. Only the 'docs' and 'src' folders

D. All folders in the repository

Solution

1. Step 1: Understand the effect of 'git sparse-checkout set'

   This command sets which folders to include in the working directory.

2. Step 2: Analyze the given folders

   Setting 'docs' and 'src' means only these two folders will be checked out and visible.

3. Final Answer:

   Only the 'docs' and 'src' folders -> Option C

4. Quick Check:

   Set folders = only those folders appear [OK]

Hint: Set folders to include with 'git sparse-checkout set' [OK]

Common Mistakes:

• Assuming all folders remain
• Thinking it excludes specified folders
• Expecting files outside these folders to appear

4. You ran git sparse-checkout set src but still see all folders. What is the likely mistake?

medium

A. You forgot to run git sparse-checkout init --cone first

B. You used the wrong folder name in the set command

C. You need to delete the .git folder to apply changes

D. Sparse checkout does not work on folders, only files

Solution

1. Step 1: Check sparse checkout initialization

   Before setting folders, you must initialize sparse checkout with git sparse-checkout init --cone.

2. Step 2: Understand why all folders appear

   If not initialized, sparse checkout settings are ignored, so all folders remain visible.

3. Final Answer:

   You forgot to run git sparse-checkout init --cone first -> Option A

4. Quick Check:

   Init missing = no sparse effect [OK]

Hint: Always init sparse checkout before setting folders [OK]

Common Mistakes:

• Skipping initialization step
• Deleting .git folder unnecessarily
• Believing sparse checkout works only on files

5. You want to work only on the frontend and backend/api folders in a large repo. Which sequence of commands correctly sets this up?

hard

A. git sparse-checkout init --cone
git sparse-checkout set frontend backend/api

B. git sparse-checkout set frontend backend/api
git sparse-checkout init --cone

C. git sparse-checkout init
git sparse-checkout set frontend backend/api

D. git sparse-checkout init --cone
git sparse-checkout add frontend backend/api

Solution

1. Step 1: Initialize sparse checkout with cone mode

   Use git sparse-checkout init --cone to enable sparse checkout in cone mode.

2. Step 2: Set the folders to include

   Use git sparse-checkout set frontend backend/api to specify the folders you want.

3. Step 3: Verify command order and syntax

   Initialization must come before setting folders; 'add' is not a valid command.

4. Final Answer:

   git sparse-checkout init --cone git sparse-checkout set frontend backend/api -> Option A

5. Quick Check:

   Init then set folders = correct sequence [OK]

Hint: Init sparse checkout first, then set folders [OK]

Common Mistakes:

• Setting folders before initialization
• Using 'add' instead of 'set'
• Omitting the '--cone' flag during init