I started to enter a bug for this but decided to ask the question first...
The Tools, Options, Git dialog, "Push all tags to remotes" setting directs the default state of the "Push all tags" checkbox on the "Push" dialog. That makes sense.
However, when needed, setting the "Push all tags" on the "Push" dialog RESETS the default on the Tools Options Git dialog. This seems like a bug.
Tags are used at our company for formal internal and customer releases. Only Software Configuration Managers (SCM) should ever create and thus push tags to the server. However, even SCM personnel should have the default (Tools, Options, Git, "Push all tags to remotes") unchecked.
There is some community discussions about the problems encountered deleting, renaming, moving tags. If everyone has the default set to UNchecked ... and it STAYS unchecked ... modifications to the tags can be done without the issue of deleted/old tags being reintroduced via the "Push" dialog "Push all tags" checkbox being checked.
Additionally, on the "Fetch" dialog, the "Fetch all tags" checkbox is NOT persistent as are the other 2 checkboxes. This would also be helpful to make the results of deleting, renaming, moving of tags more consistent.
Hi
Thanks for your feedback. We can take a look at the behaviours and see what we can do to ensure they are consistent. Could you please copy the contents of this question across to a new ticket to https://jira.atlassian.com under the SRCTREEWIN project?
Hi Michael,
I followed the link and got to where I think I should have been ... (I am logged in) ... selected 'Create' ... and specified SourceTree for Windows ... but the only other options that are presented is to select Issue Type (which defaulted to 'Bug', which I think is correct) ... and 'Cancel'. ... no way to add the details from above that I entered here ... or to submit it (and add later)?!?!?
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Interesting, sorry about that. I will try to bring it to the attention of our Jira colleagues.
in the meantime I've created https://jira.atlassian.com/browse/SRCTREEWIN-11298
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.