Feature: Support shallow cloning of git repositories #4561
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds support for shallow cloning of git repositories. While having the full git history available is the only way to truly be certain of the next version, this is not desirable on larger repositories with many thousands of commits as a full clone can take several minutes and is usually neither desirable nor needed as there is sufficient information (e.g. git tags) available on the N most recent commits to be able to reliably determine the next version without requiring a full clone.
Since this is a special scenario it put behind an explicit flag
allowshallow
to ensure both backwards compatibility and awareness of the user of the tool.Motivation and Context
Observation that the git checkout step on CI pipelines is taking 5-20 minutes on large internal repositories due to having to fetch the whole history as required by GitVersion. This step sometimes represents more time than the rest of the steps, leading to costs and undesirable long iteration cycles.
How Has This Been Tested?
Checklist: