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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

How can I avoid to jump to "History" after each commit?

I think this started during the last months when I did not work much in code. When I make a commit in Sourcetree under "File Status" the view jumps to "History" all the time where I can see all commits. But I want to stay under "File Status" as other changes are not committed yet. Is there a way to avoid this as it really disturbs my workflow.

5 answers

1 accepted

6 votes
Answer accepted

Under Tools -> Options -> General there is a setting down below under Commit Settings called "After committing, stay in commit dialog if there are still pending changes".

Thank you so much!!!

Like Vincent Meijer likes this

I will try this as I am having the same issue.

This DOESN'T seem to work if you uncheck 'Automatically start SSH agent when Sourcetree opens'... Really annoying and disruptive to those of us that commit a lot.

I tried the suggested answer by @Vincent Meijer but still the same problem (I don't have pending changes after commit).

I think it's a new "feature" added in 3.4.8 as I didn't have this problem before upgrade.

If so - please Atlassian undo it!  Or at least make it configurable.

Stefan Nilsson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Dec 14, 2022

I have the same problem (I don't want sourcetree to switch to the history tab when commiting the last changes). The existing option is cute I guess, but I really don't see the point of automatically switching to the history tab after a commit at all, so if we could get an option to not do that, that would be nice

How is it solved?

As of January 2023 on v3.4.11 it is NOT solved. The "accepted" answer seems to only work if the stars are aligned just right.

1 vote
Leo Gold
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Mar 23, 2023

Please add an option to not go to history on commit. Reposeed solutions don't work.

Because of the new "feature" - when I go back to File Status it doesn't update automatically, I have to refresh (F5) - which does cause issues now because it looks like there's no changes!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events