I can’t speak for the original post, but I’ve seen other people[1] increase the commit count because part of the build process looks for a specific commit to ch

I can’t speak for the original post, but I’ve seen other people[1] increase the commit count because part of the build process looks for a specific commit to checkout after cloning. If you have pull requests landing concurrently and you only clone the most recent commit, there is a race condition between when you queue the build with a specific commit id and when you start the clone. All that being said, I don’t know why you would need you build agents to clone the whole damn repo for every build. Why not keep a copy around? That’s what TFS does. One other thing I've seen to reduce the Git clone bottleneck is to clone from Git once, create a Git bundle from the clone, upload the bundle to cloud storage, and then have the subsequent steps use the bundle instead of cloning directly. See these two files for the .NET Runtime repo[2][3]. I assume they do this because the clone step is slow or unreliable and then the subsequent moving around of the bundle is faster and more reliable. It also makes every node get the exact same clone (they build on macOS, Windows, and Linux). Lastly, be careful with the depth option when cloning. It causes a higher CPU burden on the remote. You can see this in the console output when the remote says it is compressing objects. And if you subsequently do a normaly fetch after a shallow clone, you can cause the server to do ever more work[4]. 1: https://github.com/dotnet/runtime/pull/35109 https://github.com/dotnet/runtime/pull/35109 2: https://github.com/dotnet/runtime/blob/693c1f05188330e270b01a6bce8ad22ab7b33f23/eng/pipelines/common/checkout-job.yml https://github.com/dotnet/runtime/blob/693c1f05188330e270b01... 3: https://github.com/dotnet/runtime/blob/693c1f05188330e270b01a6bce8ad22ab7b33f23/eng/pipelines/common/clone-checkout-bundle-step.yml https://github.com/dotnet/runtime/blob/693c1f05188330e270b01... 4: https://github.com/CocoaPods/CocoaPods/issues/4989#issuecomment-193772935 https://github.com/CocoaPods/CocoaPods/issues/4989#issuecomm...