foxundermoon/vs-shell-format

CI/CD automate publishing to Open-VSX.org

elgalu opened this issue · 2 comments

elgalu commented

Open-VSX publishing is out of date

Thanks for your work here on this extension, highly appreciated<3

trinitronx commented

👍 +1 to this!

Looks like a helpful user @Majunko has published the extension to OpenVSX in the meantime.

In the long term, it's probably best for @foxundermoon to claim ownership on OpenVSX as the official maintainer of this extension.

For now, those of us affected by the split between OpenVSX / VisualStudio Marketplace repos for OSS builds of VSCode can use the published extension link mentioned above by @bilogic.

Background Info

OpenVSX / VSCodium vs. VSCode Extension Marketplace Split

In the past few years, many OSS Linux packagers of VSCode, VSCodium, (a.k.a. Code OSS) have moved to using OpenVSX extension Registry and had to disable Microsoft's Extensions Marketplace by default due to Microsoft's licensing restrictions (whether they be perceived or actual 🤷).

So, in order for most Linux developers using stock OSS-packaged versions of VSCode to find extensions such as this one, it's important to also publish to OpenVSX.

It's pretty simple to implement dual publishing via a GitHub Actions workflow described here. It probably wouldn't take very long to accomplish and in addition would allow for easy deployment through GitHub Actions CI/CD.

Below is some more info from OpenVSX's extension publishing letter template:

OpenVSX Info / Request Template

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.