Replies: 1 comment 2 replies
-
|
Unfortunately, I'm having a problem publishing to the OpenVSX claimed namespace. I don't have access to the Eclipse account anymore |
Beta Was this translation helpful? Give feedback.
-
|
do you think there is a way someone could help? |
Beta Was this translation helpful? Give feedback.
-
|
@raul-ghermanI I gave up on it a while back because the steps were tedious. I've emailed multiple people in the community, but I did not manage to get it sorted through the Eclipse org account support. It should be easy to revoke the agreement and republish, but the functionality is not there. |
Beta Was this translation helpful? Give feedback.
-
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
.vsixfiles 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 publishcommand to publish your extension. There's also a doc explaining the whole process with an example GitHub Action workflow.Beta Was this translation helpful? Give feedback.
All reactions