feat: Add GHES support #23
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for the PR! I've published version 3.2.0 which includes this change |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for generating user and team links when VSCode is configured with a Github Enterprise Server authentication provider, as suggested in #22 .
One consequence is links to users and teams will use the GHES url when switching to a repo that was cloned from github.com. This is an issue any plugin will face in this scenario and not unique to this one. In situations like this, it may be advisable for users to utilize VSCode's Workspace feature, keeping GHES-based repos in one Workspace and Github.com-based repos in another while syncing their extensions and settings appropriately.