Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Why Push dialog "Push all tags" checkbox override the default found on the Tools Options Git dialog?

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.

1 answer

0 votes
minnsey Atlassian Team Jan 11, 2019

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

CreateAtlassianSourceTreeIssue_Issue.png

minnsey Atlassian Team Jan 25, 2019

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

OK, thanks very much!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Sourcetree

Tip from the team: configure your repos for hosting goodness!

Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...

3,000 views 4 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you