-
Notifications
You must be signed in to change notification settings - Fork 50
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
Support multiple GitHub accounts #109
Comments
Depends on microsoft/vscode#127967 and then the copilot extension will need to take advantage of this. |
This is a critical enterprise scenario... Data isolation of enterprise accounts, potentially even sensitive customer data. We have been waiting on this for months. Please prioritize this already. |
but the main Copilot extension already works fine with a separate GitHub account! And even Copilot Labs worked. Copilot Chat extension just ignores the account selected for Copilot and instead goes for the main account used in VS Code for settings sync! I don't want to switch between VS Code profiles. I like having same settings at work and at home. But I only have Copilot enabled for the work account, which I don't use at home. |
Recently, the main Copilot extension started complaining about the github account and stopped working. I ended up setting a separate Microsoft account just for VS Code settings sync. |
For now, it's a possible workaround for some developers, but not a “real” solution. About 1.5 years ago, syncing settings with Microsoft account was suddenly a problem. After days and weeks of people here on GitHub complaining about sync issues with MS accounts and MS not doing anything about it, I switched to GitHub sync. Since then, there have been no more problems with synchronizing settings. Anyway, they should split Copilot-licensing from Copilot-settings or introduce a possibility to link private accounts to business accounts regarding the Copilot-licensing in some way. |
Now that microsoft/vscode#222131 has merged in VSCode, is there a plan to implement support for it in this extension? I still have not found a reliable way to use a different account for GitHub Pull Requests vs this extension, particularly after some of the changes around #1444 (I guess |
@ian-h-chamberlain have you tried:
|
@TylerLeonhardt I just tried these steps; I guess maybe my order of operations was part of the problem before?
Now, Copilot Chat works as expected but not Copilot itself, with several of these logs in its output channel:
I can see that Chat is using the correct account name, but Copilot is not, based on the timestamps in the "trusted extension" view: GH PR account (
|
Couple things here that would fix the issue for you:
What you could do right now... is maybe something like this:
Let me know if that works for you. |
I think this is the part where it becomes problematic... after sign-in it presents this prompt:
I'm glad to hear there is planned work being done here! I think Copilot (not Chat) using |
Update in Core: Actually I think with that change, this should be supported. |
This resolves the issue for me! Thank you. Update - it works, but you have to change it every time you open/close VSCode it seems, which is a little bit annoying. |
@claidler you shouldn't have to do that and I don't repro that behavior. Can you open a new issue please with some solid steps that you follow? |
Closing this issue since the feature is resolved (covered by test plan microsoft/vscode#229420) |
I use multiple GitHub accounts. One has access to GitHub Copilot and GitHub Copilot Chat, and the other one does not.
After installing the GitHub Copilot and GitHub Copilot Labs extensions, you are asked to sign in with your account.
After installing the GitHub Copilot Chat extension, you are not.
There is also no option to manage it under:
At the moment, I only get this error message:
![image](https://private-user-images.githubusercontent.com/123128755/240655888-2e2be985-c7c9-4724-abbc-a6651a7b6196.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5MjQxOTYsIm5iZiI6MTczODkyMzg5NiwicGF0aCI6Ii8xMjMxMjg3NTUvMjQwNjU1ODg4LTJlMmJlOTg1LWM3YzktNDcyNC1hYmJjLWE2NjUxYTdiNjE5Ni5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjA3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIwN1QxMDI0NTZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iMzVhYWU0ZGNiNDkyNjk0ZWJmYjYyN2YwMmEzNzBlOGIxMGQ0YWU2ODFjMzg4M2FiZGUwZGRlZjYzNjJmY2MxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.bzJ-JCNEHl-XKxwPBY2f4UOPgjuEXnH5Q6YFYIknLy4)
Please add an option to select the account.
The text was updated successfully, but these errors were encountered: