Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


Sourcetree context menu unusable (possibly) due to LFS



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
Status: Finished
Path: C:\Users\<USER>\AppData\Local\Temp
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).


Sourcetree v3.4.5

Bitbucket Data Center v7.13.0


Thank you!



0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events