How to clear Sourcetree push status
Asked by Roy Wong:

Usually I use sourcetree to do selective commits cause its much easier than typing in the files.

After committing, I'll do a hg push in the command line.

However, sourcetree doesn't seem to be aware that the commit has been pushed. Hence the badge number under the "push" icon has been increasing.

How do I clear this status, and bring sourcetree up to date, and aware of the current status?

What would happen if I use sourcetree to push in this instance?


Answers:
author: stevestreeting
body: SourceTree only checks the remote status compared to the local repo periodically - the frequency is set in Preferences, see the 'Check default remotes for updates every X minutes' option.

So SourceTree would have figured this out given a bit of time, but if you want to force it to happen early, use Repository \> Refresh Remote Status. This still happens in the background, but give it a few seconds (depending on the speed of the remote) and the badges will update.

When you push or pull inside SourceTree, it uses the knowledge it gets from this to update the badges immediately.

comments: author: stevestreeting
body: Strange, refreshing the remote should work, it does here. You can push in SourceTree, if there's nothing to push then nothing will happen but the numbers will be reset.


author: Roy Wong
body: I tried Repository \> Refresh Remote Status. But that doesn't work either. The number remained.

Made some commits today in Sourcetree and pushed with command line again.

The number under the "push" icon keeps on increasing.

Would it be bad if I try to push with sourcetree under this condition? As in, no actual commits to push (since hg push as done that), but clicking push in sourcetree?

Or any other ways to clear that numbers.


author: Roy Wong
body: finally tested it with another repo. yes it will end with an error "no changes found" and clear the status.


author: GriehleNEF
body: I have a similar situation except the master is set up to where I cannot push from sourcetree. Only by PR do things get into master. So my badge numbers just keep getting bigger and bigger and nothing seems to clear them out.


author: Miquel Mittertreiner
body: Gary did you solve this? And how?


author: Eugene Porubaev
body: I had the same issue.  

Sourcetree showed badge with 56, after I have 1) pushed from sourcetree 2) merged \& closed the pushed branch from bit-bucket.

Resolved by switching to master (the bage still existed) and removing :( the local branch (that was already closed/aka deleted on remote).


author: Chris Spurgeon
body: Never mind, I'm an idiot! I didn't realize I still had a pending push in a different branch. I just needed to push that. Please ignore my original comment below...
> I'm having a similar, though not identical, issue. For me the Push counter resets to "1" instead of clearing. As I make new local commits the Push counter increments correctly, and the pushes all execute correctly. But then the Push counter goes back to "1" again. "git status" and "git diff" don't show any commits waiting to be pushed, and hiting "Repository--\>Refresh Remote Status" didn't clear it.
>
> Any suggestions?


Tags: push

status