A huge monorepo can make every checkout expensive even when a developer works inside one application. The immediate goal is to make the next change safer and easier to explain. Begin with the branch state and the people who depend on it.
Why this deserves attention
Git’s official documentation separates the working tree, index and commit history because each command acts on a different part of that model. A workflow is easier to trust when teammates can see what changed, why it changed and how to recover if an assumption was wrong. Good habits matter more than memorising every flag. Sparse checkout reduces the files present in the working tree, but build scripts may still assume other directories exist. A clear explanation of the intended result is usually more valuable than a long sequence of clever commands.
A practical way forward
Choose the needed folders with Git’s sparse-checkout command and run the normal build and search workflow to expose hidden assumptions. Read git status before acting and inspect the diff afterwards. If the change affects a shared branch, communicate the plan before rewriting or merging history.
Picture it in a real situation
A team working only on documentation may keep that tree visible while still using repository history for the rest. A small, named change is easier for a teammate to review. Record the commit or branch involved so a later investigation can reconstruct the choice.
What to avoid
Avoid treating absent files as deleted from Git or enabling sparse checkout without telling teammates why their local build differs. Check whether the branch is shared and whether the command can discard work. A recovery step should be understood before a risky history operation begins.
Takeaway
Make the next change small, reviewable and recoverable. Explain the intent beside the result.
Sources and further reading: Official Git documentation; Git worktree manual.