Add fetch-depth to 0 for all jobs that builds an artifact to be released#443
Merged
spe-ciellt merged 1 commit intodevelopfrom Mar 17, 2026
Merged
Conversation
…sed. 0 is infinite depth
31b326e to
9a45e6a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When building, the git version tag is used to create a release number. A too shallow git clone will not include the last tags and will create slightly weird version numbers. It said
4.0.0whichCMakeLists.txtpicks up from the version set when initializing CMake inproject().Switched to 0 for all, which is a complete clone. Most had none from the beginning, which defaults to 1. I tried 50 first, but that was probably too shallow since
developis branched ofmainat some point.