Add Open VSX publishing for Cursor and other editors#34
Open
KyleKincer wants to merge 1 commit into4d:mainfrom
Open
Add Open VSX publishing for Cursor and other editors#34KyleKincer wants to merge 1 commit into4d:mainfrom
KyleKincer wants to merge 1 commit into4d:mainfrom
Conversation
Author
|
@guillaume-kotulski any interest in this PR? Would be good to have, as a lot of our team is using Cursor. Let me know if I can help! |
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
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 adds support for publishing the extension to the Open VSX Registry, which is used by Cursor and other editors that support VS Code extensions.
Changes
.github/workflows/publish-open-vsx.ymlthat publishes to Open VSX using theovsxCLI tool.github/workflows/publish_workflow.ymlto include the Open VSX publishing step alongside the existing VS Code Marketplace publishingSetup Required
To enable publishing, the repository maintainers will need to:
OPEN_VSX_TOKENin the repository settingsOnce the secret is configured, the workflow will automatically publish new releases to Open VSX whenever changes are pushed to the main branch.
Benefits