Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish to OpenVSX #188

Closed
akosyakov opened this issue Nov 26, 2021 · 0 comments
Closed

Publish to OpenVSX #188

akosyakov opened this issue Nov 26, 2021 · 0 comments
Labels
wontfix This will not be worked on

Comments

@akosyakov
Copy link

Unfortunately, MS prohibits the usage of MS marketplace by any other products or redistribution vsix files from it. Because of it we kindly ask you to take ownership of your namespace in OpenVSX and publish it there as well.

OpenVSX is a vendor-neutral alternative to MS marketplace used by all other derivatives of VS Code like Gitpod, OpenVSCode, VSCodium, Theia based IDEs, and so on.

The docs for publishing the extension are here. Technically this should be straightforward. You get a token and call ovsx publish with it. For example, this is how RedHat publishes their java extension.

Let me know if you are open to a PR contributing release GH action both to MS marketplace and OpenVSX. You can find an example of such action here.

@equinusocio equinusocio added the wontfix This will not be worked on label May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants