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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Feature Suggestions for streamlining the pulling process!

I think SourceTree is a pretty great tool because it allows me to keep tabs on the HUNDREDS of repositories my team manages.  It's great to get notifications that there are new changes ... but then it gets ugly.  I've got to click the notification (or browse for the repo if I miss it) and click Pull, then I get a modal dialog that I later need to Close.  Then I've got the repo window which I also want to close. 

that's a lot of clicking for a simple operation.  I have some suggestions...

1. what about a setting that would tell the app to pull automatically if there are new changes.  Options could exist to handle situations where uncommitted changes exist locally (automatically shelve the changes, etc.)
2. What about better sorting options for the list of repositories so repos with changes I want could be grouped together?  Perhaps offer sorting by # of changes, or date of most recent change ...
3. How about an option to pull from a context-menu in the repository list?  A modal-dialog-less way to pull would be great.  If you don't have #1, I could couple this with #2 to at least easily pull changes for a bunch of repos without dealing with multiple modal dialogs.
4. The GUI should do a better job of differentiating between incoming and outgoing changes in the repository list.  Uncommited changes are dark numbers and changes ready for push or pull are light numbers.  Why not differentiate between changes ready for pull and those ready for push?  3 columns in this display  would be simple...

Thanks for reading.  These are all suggestions that I think individually or collectively could great improve the usefulness of this tool for teams with many repositories.

1 answer

1 accepted

0 votes
Answer accepted
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 10, 2018

Hi Wesley,

Please file individual tickets for each of your suggestions (if they aren't there already, please search) so other users can vote on them and we can weigh their priority accordingly when planning future releases.

For Mac: public tracker
For Windows: public tracker


Brian Ganninger
Senior Mac Developer, Sourcetree

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events