[UPDATE] Looks like there's an even simpler way of doing it here: https://github.com/EclipseFdn/open-vsx.org/wiki/Auto-Publishing-Extensions#request-an-extension-be-auto-published (They just fetch listed extensions from the VSCode marketplace once a day.)
====================================
Would be great, so that people don't have to install the vsix manually in all VSCode IDEs that aren't actually VSCode.
Most straightforward is either using this action: https://github.com/HaaLeo/publish-vscode-extension?tab=readme-ov-file#example
... or just building the vsix and dragging & dropping after registering for an account on the OpenVSX website.
They have a long guide here but having published a few extensions there myself, I don't get why they make it seem so complicated. Most things (creating a namespace, then creating a token or straight-up publishing) can be done with few clicks through their website.
[UPDATE] Looks like there's an even simpler way of doing it here: https://github.com/EclipseFdn/open-vsx.org/wiki/Auto-Publishing-Extensions#request-an-extension-be-auto-published (They just fetch listed extensions from the VSCode marketplace once a day.)
====================================
Would be great, so that people don't have to install the vsix manually in all VSCode IDEs that aren't actually VSCode.
Most straightforward is either using this action: https://github.com/HaaLeo/publish-vscode-extension?tab=readme-ov-file#example
... or just building the vsix and dragging & dropping after registering for an account on the OpenVSX website.
They have a long guide here but having published a few extensions there myself, I don't get why they make it seem so complicated. Most things (creating a namespace, then creating a token or straight-up publishing) can be done with few clicks through their website.