Duo chat not available when git remote is different server to that which extension is authenticated against
Checklist
-
I'm using the latest version of the extension (see the latest version in the right column of this page) - Extension version: 5.9.0
-
I'm using the latest VS Code version (find the latest version here) - VS Code version: 1.92.2
-
I'm using a supported version of GitLab (see README for the supported version) - GitLab version: v17.2.2-ee / happens on dot com
Summary
Duo Chat doesn't work with a folder whose git remote is different from the GitLab server that the extension is authenticated against.
Steps to reproduce
- Authenticate the extension with gitlab.com (both OAuth and PAT flow show the same issue) with an account that is enabled for Duo features
- Clone a project hosted on a different GitLab server
- Open this project in vscode
What is the current bug behavior?
Duo chat features are unavailable (including the main pane and editor context menu options).
Note that duo chat features are available if the remote is removed (e.g. close vscode, run git remote rm origin, reopen vscode)
N.B. I haven't tested this scenario against a SM server with Duo enabled
What is the expected correct behavior?
Duo features should be available.
Relevant logs and/or screenshots
Possible fixes
TBD