When multiple GitLab accounts are configured in VS Code (gitlab.com + self-hosted/private instances), authentication may return the wrong session because the GitLab VS Code extension does not support the multi-account authentication API introduced in VS Code 1.93
Cause
The GitLab extension currently targets VS Code engine 1.92.2, while multi-account session filtering support was added in 1.93.0.
GitLab issue #2266
Workaround
Use the extension in my fork https://gitlab.com/e-marchand/gitlab-vscode-extension/-/releases/multi-account
When multiple GitLab accounts are configured in VS Code (gitlab.com + self-hosted/private instances), authentication may return the wrong session because the GitLab VS Code extension does not support the multi-account authentication API introduced in VS Code 1.93
Cause
The GitLab extension currently targets VS Code engine 1.92.2, while multi-account session filtering support was added in 1.93.0.
GitLab issue #2266
Workaround
Use the extension in my fork https://gitlab.com/e-marchand/gitlab-vscode-extension/-/releases/multi-account