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.