Prepare for OpenVSX #10
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
RSDuck
reviewed
Oct 17, 2020
dscottboggs
force-pushed
the
fix/prepare-for-openvsx
branch
from
726a4bd to
38cd4a2
Compare
Closed
saem
reviewed
Oct 18, 2020
saem
requested changes
Oct 18, 2020
dscottboggs
force-pushed
the
fix/prepare-for-openvsx
branch
from
2f6ca10 to
65aa1ed
Compare
saem
approved these changes
Oct 19, 2020
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 makes #9 obsolete, and additionally removes the unnecessary dependency on
ms-vscode.cpptools(see discussion in #8), making the extension ready for publishing to both the official Microsoft extension repository as well as the OpenVSX repository.