Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Doesn't always tell you a pull is waiting

Run source tree windows app with 4 different repositories, it starts up and just sits there. Click on the different repositories, switch between file status and branches. Nothing to report. Yet I know there are changes I need to pull on two of these repositories. Click around a bit more, nothing. Eventually one of the repositories shows a 1 next to the pull button. After pulling that, the other one shows a 1. I don't get this, it can't be meant to work like that? Surely you would start up the app, then the first thing it should do is see if there are any remote changes that need pulling and warn you? I'm sat here thinking I have an up to date project, but it isn't. Sure, I'd find out when I tried to push some changes, but that might be far too late. Is it a bug or just expected behaviour?

1 answer

1 vote
Mike Corsaro Atlassian Team Oct 16, 2018

Hello! This is an expected behavior -- fetching remote changes is done in the background, and unless someone else is working on your branch it shouldn't actually impact anything. Additionally, fetching remote changes can be an expensive operation depending on your network speed and repository size (hence it being in the background)

 

However, you can manually trigger this check via the menu "Repository > Refresh Remote Status" or by running "Fetch".  You can also lower the auto refresh time by changing "Check default remotes for updates every [10] minutes" in "Options > General".

Thanks for the reply, I'll up that default check time to ever minute.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Sourcetree

Tip from the team: configure your repos for hosting goodness!

Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...

3,344 views 4 5
Read article

Community Events

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

Events near you