On my Windows install, I have to exit SourceTree and re-enter SourceTree each morning before remote fetches will work... Why?
Seems to be related to a long period of time in-between SourceTree use.
Is there another workaround (for instance, Refresh does not fix the problem).
Seems that local functions seem to work OK, but anything that is dealing with the remote, seems to fail. My Remote is on Bitbucket (if that is relevant).
Also, when the commands are sent manually from either CMD or MinGW, the commands execute. When I use the Custom Commands, they do not work (when ST is in this state). My custom commands are using CMD environment (used a custom command "which git.exe" to prove that is using Windows path to git.exe). Did a git --version and got "git version 2.8.3.windows.1". Did this in WinGW terminal, Windows CMD, and Custom Command in ST.
A re-start of ST fixes all ... but, this is very consistent.
No error - just sits forever with the scanning work progress bar looking like it is trying ... If I go out and back into ST, and try again, the action always completes immediately.
BTW - I have auto checking of remotes for updates every 10 minutes set ... I tried unchecking this box.
The behavior was changed.
When I uncheck the remote update box under General Options, I have not had to restart ST (that I have observed as of yet). Fetches and Pulls seem to work, even after long periods of time (like overnight).
Of coarse I have to manually update with a fetch, but, so far the above has not been observed. Perhaps the two are related ...
Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG