README: Add extension url in install to help distinguish from variant extensions #40
Conversation
This file contains hidden or 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
When searching for "alabaster" in VS Code, several extension variants show. Prominently adding extension url in install in Github helps users know which is the correct extension to install.
Owner
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When searching for "alabaster" in VS Code, several extension variants show. Prominently adding extension url in install in Github helps users know which is the correct extension to install.
For example, top 5 extension search results for "alabaster" in VS Code all mention "Alabaster" word as they are variants:
Additionally it would be good if the repo author could also add this VS Code extension url in Github's repo settings to make the link easier to find.