Fetch tags regardless of fetch-depth#39
Merged
thescouser89 merged 1 commit intoproject-ncl:mainfrom May 5, 2026
Merged
Conversation
thescouser89
approved these changes
May 4, 2026
Contributor
thescouser89
left a comment
thescouser89
left a comment
There was a problem hiding this comment.
Approved, but from actions/checkout#1471 , there might be a bug where fetch-tags setting is ignored if fetch-depth is set to 1.
Contributor
Author
Huh, good find. According to https://github.com/actions/checkout/releases/tag/v6.0.2 our current version is 6.0.2. Should we just try it and see before attempting workarounds? |
Contributor
|
Sounds good! Let's see if that fixes it. |
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
2 participants
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 need to fetch tags to correctly calculate the gh release tags