CODEWITHSUNDEEP
gitvisual-studio-code
Mark Williams
Mark Williams

Reputation: 459

A little confusion about the VS.code UX and git checkout

I am not a day-to-day programmer so get a little rusty with stuff now and again. I understand GIT, etc but the behavior and UX of VS.Code when using it is not clear to me.

Specifically, when I issue a "git checkout " command from the terminal, GIT responds as I would expect (in the Terminal) and confirms the change of branch. However, the VS.Code toolbar (bottom left) doesn't change and I remain in the original branch. If I exit VS.Code and run it again then I DO see the right (checked out) branch in the toolbar. Is that expected? Is the UX not responsive to a checkout?

At a broader level, what is the general workflow for changing branches within VS.Code. For example, if I have a file open BranchA is checked out and then checkout BranchB (where that file is different) then VS.Code doesn't show any change. I assume that is by design but I could also imagine getting into a bit of a pickle with what the UI shows vs. the branch and files GIT is changing.

I have searched and found a few other folks who seem to have similar confusion so hoping that there is perhaps some docs somewhere that perhaps describe the recommended workflow here.

Upvotes: 2

Views: 91

Answers (1)

VonC
VonC

Reputation: 1323943

First, make sure to install the GitLens plugin

It does come with a branch view, but also forces the bottom left VSCode toolbar widget (the Status Bar Sync) to refresh itself more often.

I usually have to wait a few seconds when switching back to VSCode before its status refreshed correctly.

Upvotes: 1

Related Questions