Remote branch not found after "Fetch" or "Pull" action

[femisimon]

Description

Remote branch not found after "Fetch" action was the message returned after making new commits and pushing commits to PR. Screenshots added

• GitHub Extension version: v2.0.15.3-alpha1
• Visual Studio version: Enterprise 2015 - Update 3

Steps to reproduce

• Have a repo that has an Open PR.
• Make sure branch is up-to-date
• Make changes to the branch and commit changes
• Click Team Explorer ==> Home Icon
• Click Sync and Push Outgoing commits
• Click Fetch/Pull on the Branch pane

Expected - Branch is up-to-date message should be returned.

Actual - Branch was not found in remote repository returned.

[grokys]

I'm unable to reproduce this, two questions:

Click Sync and Push Outgoing commits

This is in the Team Explorer "Synchronization" pane is that correct? Sync on that pane automatically pushes outgoing commits so once I've clicked it, the "Push" link is disabled.

Click Fetch on the Branch pane

Do you mean on the "Synchronization" pane again here? I can't find a "Fetch" command on the branch pane. Or do you mean on the context menu for the current branch on the branch pane?

Either way, this is strange: the "Synchronization" pane isn't our code - it's part of Team Explorer itself.

[femisimon]

@grokys I should have added Pull when I reproduced it.

Either way, this is strange: the "Synchronization" pane isn't our code - it's part of Team Explorer itself.

The issue might be introduced by our code, cause I wasn't getting this error in v2.0.15.1.

This is in the Team Explorer "Synchronization" pane is that correct? Sync on that pane automatically pushes outgoing commits so once I've clicked it, the "Push" link is disabled.

Sync will push outgoing commits

Screenshot attached as well:

[grokys]

Hmm, I stil can't quite understand - might be worth doing a screen share later today if you've got 20 mins free @femisimon ?

[femisimon]

@grokys yes, that works. Slacking you now.

[femisimon]

Closing this not reproducible.

[mrdnote]

I'm getting this error all the time when doing a fetch or pull. In the screenshot you can clearly see the item exists in the remote repo.

My workaround solution is to delete it locally and then check it out again...