Add a workflow for publishing an extension to open-vsx.org #352
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
| Cool! If it's possible, could you create the token? Maybe share it via private message with me then. If that's not possible, I can also create the account. 😃 |
| Maybe a token from your old account will work? https://open-vsx.org/extension/vscode-snippet/snippet |
| Gotcha, I've added the token now. 👍 |
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.
Closes #351
I used this github action: https://github.com/HaaLeo/publish-vscode-extension
In order for this to work, an access token named OPEN_VSX_TOKEN should be added to repository secrets (repository settings -> secrets -> actions -> new repository secret). More info: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions.