Sparse checkout: fewer working files without erasing history

Useful to know

git sparse-checkout limits which tracked paths appear in the working tree. It can simplify work on a defined part of a large repository. [1]

A locally absent directory has not necessarily been deleted from the project. Distinguish sparse checkout from shallow history and partial object downloads. They solve different problems and should not be confused when diagnosing missing data.