Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,461,070
Community Members
 
Community Events
176
Community Groups

Clicking on commit button jumps to History, how to prevent?

I usually commit my changes in batches, by staging files and chunks related to a specific subject and writing a descriptive message for each commit. Since latest SourceTree update (3.4.7.0) the behavior of Commit button seems to have changed. Now clicking on the Commit button seems to change the active view from File Status to History, pointing on the created commit. However, I would like to keep on staging more changes to create more commits. Now I have to click on File Status each time I want to create a new commit, which is rather annoying on the long run. I would like to keep the current view in the File Status until I am done with my commits. Am I missing something - is there a setting somewhere to change the behavior, or is this intentional?

1 answer

1 accepted

I am having the same issue and would like to know how to prevent this from happening. I have a workflow similar to Heikki and this behavior is annoying.  I especially don't like unexpected behavior like this in any program. It qualifies as other people making decisions for me and I don't like that.

I found the answer here. Simple, but still an annoying "feature" that we must now deselect.

https://community.atlassian.com/t5/Sourcetree-questions/How-can-I-avoid-to-jump-to-quot-History-quot-after-each-commit/qaq-p/1910034?utm_source=dm&utm_medium=unpaid-social&utm_campaign=P:online*O:community*I:social_share*

 

Brilliant, thank you very much, Anthony! Despite looking for a related setting I somehow managed to miss this one. I agree this is an annoying feature, but luckily they made it optional.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events