Add option to fetch tags even if fetch-depth > 0 #2
Conversation
This file contains 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
RobertWieczoreck
force-pushed
the
add-fetch-tags-option
branch
from
21bbf8c
to
655f7fa
Compare
RobertWieczoreck
force-pushed
the
add-fetch-tags-option
branch
from
655f7fa
to
b9d6ac4
Compare
RobertWieczoreck
force-pushed
the
add-fetch-tags-option
branch
2 times, most recently
from
c6aa48d
to
c7a760c
Compare
RobertWieczoreck
force-pushed
the
add-fetch-tags-option
branch
from
c7a760c
to
68d6795
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Same as #1 - only updated to the latest changes of the fork.
Adds an optional fetch-tags option that can be used to override the default behavior of adding the --no-tags arg to the generated git fetch command if fetch-depth is configured and not 0.
This way, users can use fetch-depth while still getting the tags inside this range, which can e.g. be important when using automatic GIT versioning plugins like jgitver.
The branch will be rebased to main from time to time, to get updated from the base repo.
Tested in Run #4424588924 in a real workflow (on a separate branch).