CI: use fetch-depth:0 for release job #788
Open
Conversation
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
We use the `git describe` command to prevent release-notes commits to create nuget prereleases for commits that have already been tagged as a "non-pre" release; see: fa788db However, this stopped working since someone upgraded the checkout action to v4: a2b2d94 What must be happening is that this new version of this action now uses a depth of 1 by default, to save bandwidth, and then the command `git describe` fails with this error: ``` fatal: No names found, cannot describe anything. ``` There's a good StackOverflow entry about this issue, and someone recommends `fetch-depth: 0` there to fix it: https://stackoverflow.com/questions/4916492/git-describe-fails-with-fatal-no-names-found-cannot-describe-anything#comment118391143_45993185
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.
We use the
git describecommand to prevent release-notes commits to create nuget prereleases for commits that have already been tagged as a "non-pre" release; see: fa788dbHowever, this stopped working since someone upgraded the checkout action to v4:
a2b2d94
What must be happening is that this new version of this action now uses a depth of 1 by default, to save bandwidth, and then the command
git describefails with this error:There's a good StackOverflow entry about this issue, and someone recommends
fetch-depth: 0there to fix it: https://stackoverflow.com/questions/4916492/git-describe-fails-with-fatal-no-names-found-cannot-describe-anything#comment118391143_45993185