Sparse checkout for partial repos in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Sparse checkout initialization output

You run these commands in a new Git repository:

git init
git remote add origin https://example.com/repo.git
git config core.sparseCheckout true
echo "docs/" > .git/info/sparse-checkout
git pull origin main

What will be the output or result of the last command?

A No files are checked out; the working directory remains empty.

B The entire repository is downloaded and checked out locally.

C Git throws an error because sparse checkout is not supported in this sequence.

D Only the 'docs/' folder and its contents are downloaded and checked out locally.

💡 Hint

Sparse checkout allows you to check out only parts of the repo you want.

Enabling sparse checkout and specifying 'docs/' in the sparse-checkout file causes Git to fetch and check out only that folder's contents.

🧠 Conceptual

intermediate

Understanding sparse-checkout file format

Which of the following lines in the .git/info/sparse-checkout file will include all files inside the 'src' directory and its subdirectories?

A src/*

B src/

C /src

D src

💡 Hint

Trailing slash means directory and all contents.

The pattern 'src/' includes the directory and all its contents recursively. 'src/*' includes only immediate children, not subdirectories.

🔀 Workflow

advanced

Steps to enable sparse checkout on an existing repo

You have cloned a large repository fully. Now you want to enable sparse checkout to keep only the 'config/' folder locally. Which sequence of commands correctly achieves this?

A git config core.sparseCheckout true<br>echo "config/" > .git/info/sparse-checkout<br>git read-tree -mu HEAD

B echo "config/" > .git/info/sparse-checkout<br>git config core.sparseCheckout true<br>git checkout HEAD

C git sparse-checkout init<br>git sparse-checkout set config/

D git config core.sparseCheckout true<br>git checkout config/

💡 Hint

You must enable sparse checkout, set the patterns, then update the working tree.

Enabling sparse checkout, writing the pattern, and running 'git read-tree -mu HEAD' updates the working directory to match the sparse patterns.

❓ Troubleshoot

advanced

Sparse checkout not working as expected

You enabled sparse checkout and set the sparse-checkout file to include 'app/'. But after pulling, you still see all files checked out. What is the most likely cause?

A The core.sparseCheckout setting is not enabled (false).

B The remote URL is incorrect.

C The branch name is misspelled in the pull command.

D The sparse-checkout file has incorrect file permissions.

💡 Hint

Sparse checkout must be explicitly enabled in Git config.

If core.sparseCheckout is false, Git ignores the sparse-checkout file and checks out the full repo.

✅ Best Practice

expert

Efficient sparse checkout with Git's built-in commands

Which command sequence uses Git's built-in sparse-checkout commands to initialize sparse checkout and set it to only the 'frontend/' and 'backend/' folders?

A git config core.sparseCheckout true<br>echo "frontend/\nbackend/" > .git/info/sparse-checkout<br>git read-tree -mu HEAD

B git sparse-checkout init<br>git sparse-checkout add frontend backend

C git sparse-checkout init --cone<br>git sparse-checkout set frontend backend

D git sparse-checkout enable<br>git sparse-checkout include frontend backend

💡 Hint

Use the new sparse-checkout commands with cone mode for simplicity.

The 'git sparse-checkout init --cone' enables cone mode, and 'git sparse-checkout set' sets the folders to include efficiently.

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