Use --no-prune-tags in git fetch command #682
Open
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.
Documentation for --prune-tags says:
I had fetch.prunetags set in my .gitconfig because normally I want to delete outdated tags. But I hadn't realized that this causes my newly-created local tags to be deleted. It seems harmless to use --no-prune-tags in the git fetch command.
The option was added in Git 2.17.0. Ubuntu 18.04 has 2.17.1, Debian buster has 2.20.1, RHEL 8 has 2.18.something.