Branches view used to indicate missing upstream branch #4073
phil-dotchon
started this conversation in
Feedback
Replies: 1 comment
-
@phil-dotchon Have you fetched recently? If so, and you still don't see the correct state, can you open an issue with repro steps and logs? I tried to replicate this, but I'm seeing the missing upstream as expected. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have recently moved to a new employer and as a reult have setup a new installation of VS code, and jumped to a much newer version. I'm not sure what versions of VS code and Gitlens I had previously.
In my past setup, when I merged a PR in GitHub the 'remote' branch was automatically deleted in the web interface
.
When I then refreshed (git fetch) my list of branches in VS Code source control, the main branch would turn red and a hover would indicate I needed to pull. At the same time, my (now deleted) feature branch would also change colour and a hover would tell me the branch was missing upstream, indicating it had been deleted and was now redundant.
In the new version this 'missing upstream' doesn't seem to work, in fact the hover tells me the branch is up to date with the remote, even though the remote has been deleted.


If I try to fetch this branch I see an error saying 'unable to fetch branch from origin'
Is there some configuration setting I need to alter to get this functionality back as it was before?
Beta Was this translation helpful? Give feedback.
All reactions