This repository has been archived by the owner on Jan 31, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 156
Publish IBM Blockchain to OpenVSX #3085
Labels
Comments
Hi @filiptronicek, thanks for getting in touch, publishing to OpenVSX sounds like a good suggestion. I'll do some investigation but tentatively we would be open to a PR to help with this. |
Looks like the extension was published to OpenVSX.. |
@mbwhite good catch, indeed it was, we publish some extensions via the https://github.com/open-vsx/publish-extensions repository, which is a very basic way of not having to do any setup on the extension side. This publishing flow recently broke for this extension (see corresponding issue), thought, and this is why I have approached the project 🙂. |
filiptronicek
changed the title
Publish IBM Blockchain
Publish IBM Blockchain to OpenVSX
Feb 9, 2022
See #3183 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Description
A big hello to the IBM Blockchain team 👋!
Unfortunately, Microsoft prohibits the usage of the MS Extension Marketplace by any other non-microsoft products. Because of this, we kindly ask you to take the ownership of your namespace in OpenVSX and publish there as well.
OpenVSX is a vendor neutral alternative to the MS Marketplace used by all other derivatives of VS Code like Gitpod, OpenVSCode, VSCodium, Theia based IDEs, and so on.
The docs for publishing the extension are here: eclipse/openvsx/wiki/Publishing-Extensions. Technically this should be straightforward. You get a token and call
ovsx publish
with it. For example, this is how RedHat publishes their Java extension: https://github.com/redhat-developer/vscode-java/blob/5d4f8d58b8e919534800ca7bc41e8513c288f573/Jenkinsfile#L78-L82.Please do let me know if you are open to receive a PR contributing a release GitHub Action both to MS marketplace and OpenVSX. I'd love to help out!
Existing issues
I removed some sections from the issue template, as they seemed to be for issues and feature request for the extension itself.
The text was updated successfully, but these errors were encountered: