You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm using the latest Sourcetree version (220.127.116.11) with the following settings:
However, Sourcetree will not refresh anything until I click on Fetch/Pull or close the entire program and open it again.
Even my working copy files won't be refreshed until I close the program and open it again!
I suppose that you can imagine how annoying this is to constantly open and close Sourcetree just to be able stage your own files in order to commit them.
Is this a known problem or is there a working solution for this?
(By the way, I've already tried un-installing and re-installing Sourcetree without any improvements.)
Thank you in advance for any help!
Hello! If you hit F5 to refresh, does that work? Additionally, can you check the per-repo settings and check if "Automatically refresh" is enabled? To do that:
Alternatively, you can uncheck "Refresh automatically when application is not in focus". Unchecking that box will cause Sourcetree to refresh only when you focus on the app, so switching back and forth should trigger a refresh.
Hmm... could you try the second part of my answer? Try unchecking "Refresh automatically when application is not in focus" in the general settings and see if Sourcetree refreshes when you switch back to the application.
If that doesn't work, the only other thing I can think of is that you may have an anti-virus that prevents Sourcetree from detecting file changes via the file watcher. If you suspect that an AV is not interfering then we can move on and I can give you steps to giving me a log file.
me and my coworker use same version of updated windows 10 and updated client in same project with same network and same everything but in my client refresh works and in the client of my coworker not, he needs to press F5 anytime.
bug has a low priority ... this is madness!
This has been an issue for me for months. Fresh install following documentation on how to clear all Source Tree settings and it still occurs.
I have noticed on smaller repos this seems to not be an issue, however on large repos I have to constantly press F5 on the Commit screen when staging/unstaging files.