Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using different Github accounts for VS Code Setting Sync and for Copilot Chat #698

Closed
aderbenev-intermedia-com opened this issue Dec 22, 2023 · 2 comments
Assignees
Labels
duplicate This issue or pull request already exists

Comments

@aderbenev-intermedia-com
  • VS Code Version:
    Version: 1.86.0-insider
    Commit: 9621add46007f7a1ab37d1fce9bcdcecca62aeb0
    Date: 2023-12-20T05:36:57.756Z
    Electron: 27.1.3
    ElectronBuildId: 25612240
    Chromium: 118.0.5993.159
    Node.js: 18.17.1
    V8: 11.8.172.18-electron.0
    OS: Windows_NT x64 10.0.19045
  • OS Version: 10 22H2

Steps to Reproduce:

  1. Sign in to VS Code with GitHub for settings sync
  2. Sign in to Copilot extension with a different Github account for Copilot access

(it works at this point)

  1. Enable Chat extension
  • it complains that my Copilot license is expired.

The account I'm using for VS Code settings sync is my old account, which had Copilot enabled for about a year;
the account I have Copilot license enabled now in is a company-bound account (this one).

Copilot itself and Copilot Labs work, but Chat doesn't and it complains on each VS Code start about that.

@github-actions github-actions bot added the triage-needed Issues needing to be assigned to the prospective feature owner label Dec 22, 2023
@Falven
Copy link

Falven commented Dec 22, 2023

#109

@LogicDaemon
Copy link

I'd rather not use chat at all (and currently I'm not using it, despite Copilot extension installs the chat every time, and then Chat disables it if I disable Chat, though the main Copilot extension working flawlessly without Chat).

@roblourens roblourens added the duplicate This issue or pull request already exists label Dec 30, 2023
@github-actions github-actions bot removed the triage-needed Issues needing to be assigned to the prospective feature owner label Dec 30, 2023
@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Aug 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

4 participants