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
Thanks for creating this extension, @ShawnZhong! I'd love to be able to install it also from the Open VSX marketplace. Would you consider publishing it there?
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 Open VSX 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; or use this GitHub Action to publish it automatically.
The text was updated successfully, but these errors were encountered:
Thanks for creating this extension, @ShawnZhong! I'd love to be able to install it also from the Open VSX marketplace. Would you consider publishing it there?
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 Open VSX 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; or use this GitHub Action to publish it automatically.The text was updated successfully, but these errors were encountered: