fix(ci): add fetch-depth: 0 to fix tag checkout on release trigger#32
Merged
Conversation
With fetch-tags: true and the default fetch-depth: 1, git fails to fetch a tag-triggered workflow because it cannot map both the commit SHA and refs/tags/<tag> to the same local ref in a shallow clone. Signed-off-by: Jimisola Laursen <jimisola@jimisola.com>
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.
Summary
fetch-depth: 0to theactions/checkoutstep intypescript-publish-to-vscode.ymlCannot fetch both <sha> and refs/tags/<tag> to refs/tags/<tag>error that occurs when a release triggers the publish workflow withfetch-tags: trueand the default shallow clone (fetch-depth: 1)Root cause
With
fetch-depth: 1(shallow) +fetch-tags: true, git's fetch refspec includes both the commit SHA and the tag name pointing to the same local ref. Git rejects this as ambiguous. Usingfetch-depth: 0(full clone) avoids the conflict.Test plan