[CI] Configure build/publishing of VSCode extension #17
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
|
Should I also include #16 before merging? I don't know how urgent this is. |
Philipp15b
reviewed
May 17, 2024
Philipp15b
reviewed
May 17, 2024
Also restructured workflow files. Unfortunately, GitHub Workflows cannot be placed into subfolders. As a workaround I use - as a separator
|
Now also includes publishing to OpenVSX. Files have been renamed to use |
Philipp15b
approved these changes
May 18, 2024
|
Thanks! |
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 builds the VSCode extension and adds the vsix-package as an asset to the GitHub release.
When a tagged release is published, the extension is published to the VSCode Marketplace (similar to publishing of Docker images to the registry).
As I find the handling of pre-releases in the VSCode marketplace strange (https://code.visualstudio.com/api/working-with-extensions/publishing-extension#prerelease-extensions), e.g. not compatible with semver, and I don't know how we should handle this, there is currently no support for automatic publishing of 'nightly' versions of the extension. The workaround for this is to manually download and install the extension from the GitHub release. But TBH I believe there is currently no need for nightly releases of the extension, so this should be fine.
Also restructured workflow files. Unfortunately, GitHub Workflows cannot be placed into subfolders. As a workaround I used # as a separator.