Option to push all tags at once 🏷

48 votes

As a user, I would like the option to push all tags at once from GitKraken.

This would be the equivalent of the `git push --tags` command.

Not planned Suggested by: Axel Pardemann (17 Jun, '21) • Upvoted: 08 Dec, '23 • Comments: 12

Comments: 12

28 Jul, '21
Jonathan Admin
Hi, I'm an engineer on the GitKraken team.
In the Long Long Ago, another git GUI (of the kind that inspired us to create GitKraken) made the questionable decision of making this functionality very, very prominent in their push dialog. We've found that most users who request this feature have simply learned a bad habit from this other GUI.
The truth is, pushing ALL tags ALL the time can cause big headaches for your team, because they're "stickier" than remote branches. That's why lots of devs see this prominent feature as a problem!
Like Peter: https://community.atlassian.com/t5/Sourcetree-questions/Why-Push-dialog-quot-Push-all-tags-quot-checkbox-override-the/qaq-p/973403
And Oliver: https://community.atlassian.com/t5/Sourcetree-questions/Can-you-please-make-the-default-status-of-quot-Push-all-tags/qaq-p/971859
For people who are CERTAIN that they NEED to do this frequently, we'd love to hear more from you. We want this client to work for everybody - but without the foot-guns.

-Jordan
29 Jul, '21
Axel Pardemann
I understand the issues from the 2 posts you have linked. Just to clarify: I wasn't talking about an automatic config to push all tags on push, just a manual option to use consciously.

I am, however, aware that introducing this where the team dynamic is more convoluted could become an issue if the devs abuse this function without thinking of the consequences of doing running such a command without properly syncing from origin first and removing tags that could be lingering locally still.

If this could be a problem I'm fine to revert to the command line and run a `git push --tags` when needed.

Thanks for the time you took to give a proper response Jordan!
11 Aug, '21
Mark van Renswoude
I'd like to add my feedback, as I've requested this feature before when I was not aware of the arguments against it. Coming from SourceTree, I do recognize the issue with tags being hard to correct once they've been pushed.

The issue we're having is that our build uses GitVersion to determine the product's version number, which for the master branch relies on the tag created when finishing a GitFlow release. Right now we need to manually push the tag first, then the master branch, to ensure the build can use the tag.

So while we do not necessarily need a "push all tags" option in this case, we do want to push the tags for the commit(s) that are behind when pushing the branch, so the developers can't forget.

If that is hard to detect/implement however, having the "push all tags" option (default off?) would solve it as well as all our developers use GitFlow, so we rarely have issues with that.
21 Sep, '21
Joey Kelroy Admin
"Add an optional push method to automatically include tags associated to local commits" (suggested by J.Morales on 2021-09-20), including upvotes (1) and comments (0), was merged into this suggestion.
01 Oct, '21
Drazen DOTLIC
Personally, respecting `--follow-tags` would - for what **I** imagine to be a typical case - be enough. Especially if you don't expose this setting in the UI - there's _very_ little chance for a foot gun here IMO.
08 Nov, '21
Danny Schneider
I liked the mecurial approach: adding a Tag is a commit. You added a Tag, history is changed, a VCS is there to document everything what happened. You should not delete things, if it is impossible to see that things are deleted or why. This is why I also do not like git branch concept at all (e.g. deleting branches). I never delete branches. So pushing all tags is in my opinion the only thing that's making sense. People who do not want to have a cluttered server repository, in my opinion have not understand what a VCS is for.
08 Nov, '21
Thomas Michiels
i have to agree with the admin here, pushing all tags has never ever in the history of tags that i know been a good idea.
Something that *might* be useful though is pushing a tag to all remotes. but please no automatic tags, tags aren't meant to be automated as they indicate rare important moments in the code, like a deploy. and gitkraken does not handle deploys (yet)
18 Apr, '22
Pawel Cioch
Basically we want a button next to Push like an arrow next to Pull, where you could do "push all tags" and git command is 'git push origin --tags'
01 Nov, '22
Guillaume Hébert
It would at least be pertinent to automatically push the tag (or at least offer the option) when finishing a gitlfow release or hotfix.
Click to enlarge

23 Aug, '23
Merab Aghniashvili Merged
it will be great if we were able to push tags with the current commit like it is in SourceTree. this is very useful in case you have CI/CD pipeline that only works with tagged commits.
24 Aug, '23
Joey Kelroy Admin
"Push commit with Tags" (suggested by Merab Aghniashvili on 2023-08-23), including upvotes (1) and comments (0), was merged into this suggestion.
08 Dec, '23
Luke M
I don't see value in the request as written—"Option to push all tags at once"—but since many tag-related requests seem to get merged into this one, I figure I'll note my request here:

+1 for the feature of "Push commit with Tags". Or, at the very least, I would like to request some visual differentiation of whether a tag resides locally, in the remote, or both—just like GitKraken does for branches. Right now the only way to distinguish a local tag from a remote tag is to right-click and infer from the available context menu options.