You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, as Microsoft prohibits usages of the Microsoft marketplace by any other products or redistribution of .vsix files from it, in order to use VS Code extensions in non-Microsoft products, we kindly ask that you take ownership of the VS Code extension namespace in OpenVSX and publish this extension on Open VSX.
What is OpenVSX? Why does it exist?
OpenVSX is a vendor neutral alternative to the MS marketplace used by most other derivatives of VS Code like VSCodium, Gitpod, OpenVSCode, Theia based IDEs, and so on.
How can you publish to Open VSX?
The docs to publish an extension can be found here. This process is straightforward and shouldn't take too long. Essentially, you need an authentication token and to execute the command ovsx publish to publish your plugin. See this example from RedHat publishes their Java extension: redhat-developer/vscode-java@ff51dbf/Jenkinsfile#L73-L82
You can also find an example PR that contributes a release GitHub Action which publishes to GitHub, MS and OpenVSX at the same time.
The process should tie in pretty nicely with any existing publishing scripts, which I wanted to contribute to, but unfortunately could not find the source code of the VS Code extension itself.
If you have any questions about Open VSX or anything regarding the publishing process, please do ping me.
With warm greetings from Prague, Filip.
The text was updated successfully, but these errors were encountered:
Hello to the entire iolevel team 👋!
Please publish the PeachPie for Visual Studio Code extension to the Open VSX marketplace.
Context
Unfortunately, as Microsoft prohibits usages of the Microsoft marketplace by any other products or redistribution of
.vsix
files from it, in order to use VS Code extensions in non-Microsoft products, we kindly ask that you take ownership of the VS Code extension namespace in OpenVSX and publish this extension on Open VSX.What is OpenVSX? Why does it exist?
OpenVSX is a vendor neutral alternative to the MS marketplace used by most other derivatives of VS Code like VSCodium, Gitpod, OpenVSCode, Theia based IDEs, and so on.
How can you publish to Open VSX?
The docs to publish an extension can be found here. This process is straightforward and shouldn't take too long. Essentially, you need an authentication token and to execute the command
ovsx publish
to publish your plugin. See this example from RedHat publishes their Java extension: redhat-developer/vscode-java@ff51dbf/Jenkinsfile#L73-L82You can also find an example PR that contributes a release GitHub Action which publishes to GitHub, MS and OpenVSX at the same time.
The process should tie in pretty nicely with any existing publishing scripts, which I wanted to contribute to, but unfortunately could not find the source code of the VS Code extension itself.
If you have any questions about Open VSX or anything regarding the publishing process, please do ping me.
With warm greetings from Prague, Filip.
The text was updated successfully, but these errors were encountered: