Can you please make the default status of "Push all tags" option as unchecked?
Asked by Oliver Cho:

Many of our company teammates are using the SourceTree as the Git client and it is pretty good in overall.

But regarding the tagging function, we're having a very annoying problem.

Normally we don't make a tag manually by each individual but the CI system makes some tags automatically when a new build is created.

Before we settled down with an agreed convention on tag naming, there were some experimentally created tags and we wanted to clear them out in order not to make an unwanted confusion. It looked just a simple straight forward thing, and removing them from the server and my local working copy was actually done easily.

However, since the Git is a distributed system the old wrong tags were already existed in other coworker's local repositories and ++because the default status of "**Push all tags** " option is '**Checked**'++, those old tags were revived so many times when someone didn't sync their local tag with the remote server and pushed his/her commit with this option on, as the people didn't pay much attention on this option status and neither understand correctly what its impact is.

If once this situation happened we had to announce repeatedly to make sure this option is turned off and to sync their local working copy tags.

I'm not so sure how many people are struggling with this issue but it was a surely annoying thing for us.

And so I want to know making its default status as unchecked would be acceptable for other users as well.

Best regards,

Oliver Cho


Answers:
author: Ana Retamal
body: Hi Oliver!

Thanks for sharing your idea and scenario with us, it will be interesting to know if there are more users that would benefit from this. Regarding your suggestion, I highly encourage you to submit it as a Feature request, that's the way our team acknowledges the wishes from our users and the way we track how many people is interested (by voting on the feature) You can submit it at <https://jira.atlassian.com/projects/SRCTREEWIN/issues/> .

Hope that helps :)

Ana

comments: author: Oliver Cho
body: Thanks Ana for your response.

I'll submit a feature request as well. Thanks. :-)

Oliver


author: Oliver Cho
body: Added a feature request.

<https://jira.atlassian.com/browse/SRCTREEWIN-11146>


author: Ana Retamal
body: Thanks!


author: Oliver Cho
body: Just resolved this question and will check from the <https://jira.atlassian.com/browse/SRCTREEWIN-11146?_ga=2.202055513.997107602.1546824612-668307711.1545285828> issue.


author: Daniel Martinec
body: This backfired at my team as well. Please prioritize the change of the default. Thank you!


author: alok.ranjan
body: I also faced this problem while pushing the code then after un-checking "Push all tags", it got resolved.


author: Derek Gallo
body: This should be taken one step further and the "Push all tags" feature should be dropped outright. This is dangerous. Backfired on my team as well. We push to git remotes as a method of deploying apps. When the remotes for our deployment were added, Sourcetree started unknowingly deploying YEARS OLD tagged versions of our apps. The worse part is there was no apparent indication that this was happening. If it wasn't for a security monitor we have setup we might have never caught it.


author: gabriel.feo
body: To anyone else affected by this, I suggest commenting **and voting** on the open issue instead: <https://jira.atlassian.com/browse/SRCTREEWIN-11146>


author: Mukesh Kumar
body: We have provided the feature in Sourcetree 3.4.18. Please update to the latest version.