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

Number of pulls/pushes never showing for repo

I currently have four separate repos, and three of them are behaving in Sourcetree as expected, but one is not, and it's causing a lot of confusion.

I created a local repo while waiting for the BitBucket account to be set up. Once that was done, a couple of days later, I hooked my repo up to the remote account. Everything works and I can push & pull without issue... however, the numbers for pushes and pulls never, ever display (by this, I mean the numbers that appears as notifications next to the buttons, or alongside the branch names). No matter how many commits, fetches or branch merges I do, those numbers never, ever display. It's getting really confusing because I'm almost daily having to do a blind pull just in case there's anything on the remote; and I keep losing track of how many commits I have locally that have yet to be pushed, and to which branch.

Any ideas on how to rectify this?

2 answers

1 accepted

1 vote
Answer accepted

Resolved. It turns out that, unless the name of the remote source was 'origin', then it would fetch, push, pull and pull without issue, but never show any pending numbers. I had to change the name of the remote and then do a fetch, and that seems to have solved it.

minnsey Atlassian Team Dec 04, 2017

Thanks for letting us know.

Like indextwo likes this
0 votes
minnsey Atlassian Team Nov 30, 2017

Hi,

I've not seen this behaviour. Is there anything different about this repo?

HTTP vs SSH for the url?
Private vs public?
etc

The only thing that's different is that I created it as a local repo initially and did some local commits while I was waiting for the BitBucket repo to be created. Then I added the remote repo after the fact. Other than that, it's identical to all other repos that work fine (all BitBucket, on the same account, private repos).

The only thing I've noticed that was different is the remote name, which was something custom. I've now just checked 'default remote', but it hasn't made an initial difference.

Suggest an answer

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

Sourcetree for Windows - CVE-2019-11582 - Remote Code Execution vulnerability

A vulnerability has been published today in regards to Sourcetree for Windows.  The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...

4,989 views 0 12
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