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 - parameters to reduce size of pulls



We have a usecase of a large shared Git repository with many users, but certain users only wanting to pull certain data within the repo. Through the command line we can do things like sparse clones, we've noticed however that in Sourcetree many users have inadvertently pulled the entire repo resulting in over 10GB of data on their drive. I was curious what options the Sourcetree UI had for supporting a use case like this. 

We've also seen a lot of inconsistency with the size of the repository when users perform a pull through Sourcetree, some users end up with 8 to 10 GB, some with 50GB plus. What can cause these disparities?



0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events