Unable to sign in, completely broken

[SirzBenjie]

• Extension version: 0.104.1
• VSCode Version: 1.97.2 e54c774e0add60467559eb0d1e229c6452cf8447 x64
• OS: Windows Subsystem for Linux - Ubuntu
• Repository Clone Configuration (single repository/fork of an upstream repository): fork of an upstream?
• Github Product (Github.com/Github Enterprise version x.x.x): ???

Steps to Reproduce:

1. Have 2 accounts on vscode
2. Activate github pull requests
3. Suffer and be perpetually greeted by a sign in button

I am just greeted by this every time. I click sign in and it does nothing.

I have basically the same symptoms as #5785

[alexr00]

@SirzBenjie can you manage which account the extension uses?

[SirzBenjie]

Clicking on that shows a list of extensions with a gear icon near each of them. I have it set to the proper profile for Github Pull requests. This is different than the profile I'm using for the github copilot extension, if that means anything.

[alexr00]

@SirzBenjie is this a public repo? Can you share the output from git remote -v?

[TheElectronWill]

Note: if your remote is not named "upstream" nor "origin", you need to change the extension settings. Otherwise you will get this in the logs, and the dreaded "You have not signed yet" message.

2025-05-22 15:54:53.022 [info] [GitHubServer] Received fallback response from the server: {"error":"API V3 is no longer supported. Use API V4 instead."}
2025-05-22 15:54:53.194 [info] [Activation] Git initialization state changed: state=initialized
2025-05-22 15:54:53.194 [info] [Review+0] Validate state in progress
2025-05-22 15:54:53.194 [info] [Review+0] Validating state...
2025-05-22 15:54:53.194 [warning] No remotes found. The following remotes are missing: origin, upstream
2025-05-22 15:54:53.194 [info] [FolderRepositoryManager+0] No GitHub remotes found for folder /home/[...]
2025-05-22 15:54:53.205 [info] [FolderRepositoryManager+0] Trying to use globalState for assignableUsers.

Solution: add your remote to this list in VSCode settings

[olejorik]

Just visiting this setting, adding and deleting a name helped me to solve this issue.

Note: if your remote is not named "upstream" nor "origin", you need to change the extension settings. Otherwise you will get this in the logs, and the dreaded "You have not signed yet" message. ... Solution: add your remote to this list in VSCode settings

[SirzBenjie]

I no longer have this problem. Not sure what fixed it.