Closed omhomurlu closed 1 year ago
@omhomurlu (Hello, I had my notifications turned off so it took me quite a while to notice. My apologies.)
If you really need this extension, please send a Pull Request with the Github Actions added. Or you can register it on your own since this repository is MIT licensed.
Otherwise, sorry, but I am busy and this will not be done right away.
On second thought, since we are using semantic-release-vsce
, this can be accomplished simply by adding OVSX_PAT
to the release.yml.
Dear extension author, Please publish this 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 Open VSX and publish this extension on Open VSX.What is Open VSX? Why does it exist?
Open VSX 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.
You can read on about Open VSX at the Eclipse Foundation's Open VSX FAQ.
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
ovsx publish
command to publish your extension. There's also a doc explaining the whole process with an example GitHub Action workflow.