Question

Your team maintains a very large Git monorepo in Azure Repos that is over 200 GB with hundreds of thousands of files. Developers report that cloning and running everyday Git commands (status, checkout) is extremely slow because they only work in a small subset of directories. You want to improve local performance without splitting the repository. Which approach should you implement?

Accepted Answer

Register the repository with Scalar to enable partial clone and sparse-checkout, downloading only needed objects and files on demand

Answer

Enable Git LFS for all source code files so that only pointers are stored locally until files are accessed

Answer

Run 'git gc --aggressive' on the server-side repository to repack objects and reduce clone size for all developers

Answer

Create a shallow clone with '--depth 1' and instruct all developers to use only shallow history permanently