vscode: VSCode can't sign in with GitHub and creates endless boxes in the "Source Control" panel

Version: 1.54.1 (user setup)
Commit: f30a9b73e8ffc278e71575118b6bf568f04587c8
Date: 2021-03-04T22:38:31.419Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Windows_NT x64 10.0.18363

It doesn’t stop making these little boxes in the “Source Control” panel. If I let it run, it eventually slows my computer to a crawl until I close VSCode.

It says I’m not signed in to any accounts. There was a moment when for no apparent reason it said I was signed in with GitHub (this was after the Live Share buttons stopped working, and even though it said I was signed in with GitHub they still did nothing). I signed out of it thinking it would remove any invalid sign in kind of state, but instead it went back to the regular broken state.

In a folder without a repo, there is an “Initialize Repository” button that effectively starts a repo and keeps making the little boxes. The “Publish to GitHub” button does absolutely nothing.

When I started reporting this bug, the “Share” button would let me sign in with Microsoft, and clicking to sign in with GitHub would say “Starting collaboration session: Auth token returned by github provider is empty.” But after signing in and back out with Microsoft, neither button does anything.

Steps to Reproduce:

I don’t know how it happened, just that it started when Live Share wasn’t working properly. Disabling/uninstalling Live Share and GitHub extensions did nothing to help.

Does this issue occur when all extensions are disabled?: Yes

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 7
Comments: 32 (10 by maintainers)

Most upvoted comments

Works for me too now!

Camto on Mar 16, 2021

Just upgrade to 1.54.3 Very happy with this. Thanks!

pattarika on Mar 16, 2021

Looks good on 1.54.3, thanks!

suwayyah on Mar 16, 2021

Related?

Remote-SSH does not work with 1.54 and --extensions-dir option (#118812)

z387-hq on Mar 12, 2021

I’ve pushed a logging change coming in the latest insiders (should be released relatively soon). Hopefully that will help pinpoint things better.

eamodio on Mar 9, 2021

Yes, I think I mentioned the version as well earlier.

suwayyah on Mar 8, 2021

This only happens for me when I open Vscode using Git Bash command.

This is the output of git:

> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir

hamza512b on Mar 8, 2021

I have the same problem (without any live share) by opening any repository. Same for vs code insider 1.55. Reverting back to vscode 1.53.2 seems to be a good temporary solution.

suwayyah on Mar 7, 2021