Git is a distributed version control system, so by default each Git repository has a copy of all files in the entire history. Even moderately-sized teams can create thousands of commits adding hundreds of megabytes to the repository every month. As your repository grows,
https://devblogs.microsoft.com/devops/introducing-scalar/
* Context switches harm developer productivity * the Windows OS repository * VFS for Git * using a custom trace system * the commit-graph file * git push * sparse-checkout * Scalar * GVFS protocol * comment on this issue * share our plan for contributing these features to the Git client * get started with Scalar * download and install the latest Scalar release * a custom version of Git * run maintenance in the foreground * Azure Repos * Git sparse-checkout feature in cone mode * a src directory one level down * most common Git commands * Git’s sparse-checkout feature * the fsmonitor Git feature * Watchman * originally contributed the fsmonitor feature to Git * continue to contribute improvements * GVFS protocol * Git partial clone feature * the git gc --auto command * setting gc.auto to zero * config step * a hook that communicates with Watchman * fetch step * git fetch with a custom refspec * Git commit-graph * it is enabled * incremental file format * delta encoding * loose objects step * the Git multi-pack-index file * pack-file maintenance step * the recent updates to the sparse-checkout feature * the partial clone feature in Git * Git Merge 2020 * give Scalar a try * create an issue