What is the purpose of Git's "sparse-checkout" feature, and what problem does it solve for very large repositories (monorepos)?
Correct! Well done.
Incorrect.
The correct answer is A) Sparse-checkout lets a clone populate the working directory with only a subset of the repo's files/directories, while still having the full object database and history available, reducing time and disk space for working in a small part of a huge monorepo
Correct Answer
Sparse-checkout lets a clone populate the working directory with only a subset of the repo's files/directories, while still having the full object database and history available, reducing time and disk space for working in a small part of a huge monorepo
This is especially useful for monorepos where a single developer might only need to work within one project's subdirectory — sparse-checkout avoids checking out potentially massive amounts of unrelated code into the working directory while preserving full history access for the included paths.