Cherry-Pick: create VSIX pipeline fixes (#537)#538
Merged
Conversation
ghost
added
the
Scottj1s
approved these changes
Mar 8, 2021
erik0686
force-pushed
the
user/ertorres/cp-vsix-pipeline-fixes
branch
from
3b093c6 to
3671834
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
A few days ago I created a PR that created a pipeline to produce a signed VSIX. Said PR was merged into main and then cherrypicked ( #537 ) into release/project-reunion-2103. There, we saw that there were some extra things that were not needed, like an installation of VSSDK and we fixed them there. So now I am Cherry picking those changes into main as well :)