I'm a long-time friend of Sourcetree, thank you Atlassian!
Now, I have a necessity to use Sourcetree with a big repo (>4.5 GB, without the .git folder). LFS content is also big (>2.8 GB), with the long list of files (>2000).
(EDIT: I've just noticed, the same behaviour can be reproduced on a small, one-file repo too - my note on how big is the repo/LFS is irrelevant.)
When using Sourcetree (workspace: history or file status), right-click on a filename (staged/un-staged files) brings up the file context menu (screenshots for an example).
It takes ages (ok, 2-3 seconds) for the menus to pop-up. Same applies for any action in the menu - it takes ages for any action to be highlighted.
The process viewer ("Tools/Process Viewer...") shows for any of these actions the "git lfs call".
Command: git lfs version
Duration: 00:00:00 (this takes longer actually :) )
Caller Context: GetLargeFileSupportVersionProcess
My questions are:
Is this a bug or a feature? If feature, then the feature makes SourceTree non-usable.
For repos (also large ones) without LFS content, this context menu works fine.
What are the possibilities this to be fixed?
Basically, this makes a difference of using or not using the Sourcetree client for us (a relatively high number of devs).
Bitbucket Data Center v7.13.0
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 an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events