In our enterprise, we currently have two GitHub Enterprise:
- github.example.com --> source code, PR's, etc.
- example.ghe.com --> Copilot License
When I sign in to the GitHub Pull-Request extension, it sets the setting:
"github-enterprise.uri": "https://github.example.com"
This will be picked up by GitHub Copilot and since the licenses are on example.ghe.com, I loose my copilot access.
If I try to login to "example.ghe.com" in Copilot, it opens the wrong URL for the login process (github.example.com) and the login cannot complete (because I started it with example.ghe.com).
When I delete the setting value again, I can perform the login to GHE but then I loose access to github.example.com n the PR extension.
Is there a workaround to overcome this issue?
- Extension version: 0.146.0
- VSCode Version: 1.123.0
- OS: Windows
- Repository Clone Configuration (single repository/fork of an upstream repository): Single
- GitHub Product: GitHub Enterprise
Steps to Reproduce:
- (see above)
In our enterprise, we currently have two GitHub Enterprise:
When I sign in to the GitHub Pull-Request extension, it sets the setting:
This will be picked up by GitHub Copilot and since the licenses are on example.ghe.com, I loose my copilot access.
If I try to login to "example.ghe.com" in Copilot, it opens the wrong URL for the login process (github.example.com) and the login cannot complete (because I started it with example.ghe.com).
When I delete the setting value again, I can perform the login to GHE but then I loose access to github.example.com n the PR extension.
Is there a workaround to overcome this issue?
Steps to Reproduce: