Ability to change Github Sign Ins between profiles

[tuscen]

I'd like to use a single VS Code instance for my private and my company work. I use separate profiles, but I also need separate Github sign ins. But it seems that Github Sign In is global to a a single VS Code installation.

[TylerLeonhardt]

You are able to change the preference which will change for the current workspace:
https://code.visualstudio.com/updates/v1_94#_change-an-extensions-account-preference

Does this solve your scenario?

[tuscen]

Tyler James Leonhardt (@TylerLeonhardt) It seems to be working, but the overall user experience feels cumbersome since I have to manually update the preferred account for each extension when switching profiles. Ideally, it would function more seamlessly—similar to remote development—where changing profiles spawns a new VS Code instance with its own set of extensions and accounts (GitHub, Microsoft, etc.).

[TylerLeonhardt]

I have to manually update the preferred account for each extension when switching profiles

You shouldn't have to manually change this each time you switch profiles. That's a bug.

its own set of extensions and accounts (GitHub, Microsoft, etc.).

Profiles aren't a high level component than accounts though. In fact they are disjointed.

You can create as many Profiles as you want independently of what accounts you have signed in to VS Code.

You only get to sign in to one account for Settings Sync... and if swapping profiles meant also swapping accounts then you'd have to maintain two instances of Settings Sync data.

But, with Settings Sync, one of the things you can sync are profiles... so it'd be very unusual if 1 account had a profile that used a different account.

Additionally, doing this "new account state per profile" is less than ideal in cases where your profiles are simply for different languages or workflows that have nothing to do with accounts. Personally, I have: a PowerShell profile, a Python profile, a Jupyter Notebooks profile... I want all of these to use my same account preference state.

So instead, representing account preference per-workspace, where the boundary really lies as workspaces are often associated with different silos (work, personal, etc), is more accurate to what folks do.

Anywayyy, that's a long winded way of saying, there is intention in the current design, but you did find a bug. The state of the workspace preference should persist cross-profile.

[TylerLeonhardt]

I have to manually update the preferred account for each extension when switching profiles

I just tried this and I only see this behavior when you are going to a workspace for the first time. In other words, this works fine:

• Open a workspace and sign in to GH Pull Request extension with Account1
• Now use another account using the steps called out in release notes
• Now change the profile of that workspace

For me, this does not change the account's preferred account.

This is because it's tied to each workspace... and then if the workspace doesn't have an explicit value, it uses a global value.

I think this is more a feature request to have a section in the Profile editor to say.. "inherit Extension Account Preference"

Where the Contents could allow for inheritance of accounts from the global level, or allow it to be profile specific.