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.

4 answers

1 accepted

4 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.

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.

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!

How is it solved?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events