You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 31, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 31, 2023. It is now read-only.
I unfortunately didn't notice this issue at first (made a duplicate) so I'm posting the text here, as I consider it may be helpful, but TL; DR: OpenVSX is great and I'm one of the maintainers, I can help or answer any questions 😄.
A big hello to the VS Code Ruby 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: redhat-developer/vscode-java@5d4f8d5/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!
@filiptronicek do you have an example repo that does this?
@wingrunr21 there are many, but for simpler extensions (which only depend on a couple of commands being executed) a pretty nice release action (with manual and automatic triggers, options for releasing just to certain ones) for creating GitHub Releases (with a .vsix file attached to it) and publishing to both of the Marketplaces can look like this one here: https://github.com/KamasamaK/vscode-cfml/blob/master/.github/workflows/release.yml
Thanks, as this project requires basically 2 extensions to be published (and I'm looking to wire it up to semantic release), I'll need to do some modifications.
Activity
github-actions commentedon Oct 15, 2021
This issue has not had activity for 30 days. It will be automatically closed in 7 days.
noraj commentedon Oct 15, 2021
unstale, I don't understand the utility of this bot for 95% of projects...
github-actions commentedon Dec 16, 2021
This issue has not had activity for 30 days. It will be automatically closed in 7 days.
noraj commentedon Dec 16, 2021
unstale
filiptronicek commentedon Jan 3, 2022
I unfortunately didn't notice this issue at first (made a duplicate) so I'm posting the text here, as I consider it may be helpful, but TL; DR: OpenVSX is great and I'm one of the maintainers, I can help or answer any questions 😄.
wingrunr21 commentedon Jan 3, 2022
I still need to wire up Github Actions for release to both (it's planned). @filiptronicek do you have an example repo that does this?
noraj commentedon Jan 3, 2022
@wingrunr21 Found one randomly on Open VSX homepage https://github.com/dendronhq/dendron/blob/master/.github/workflows/publish-extension-dendron.yml
filiptronicek commentedon Jan 3, 2022
@wingrunr21 there are many, but for simpler extensions (which only depend on a couple of commands being executed) a pretty nice release action (with manual and automatic triggers, options for releasing just to certain ones) for creating GitHub Releases (with a
.vsixfile attached to it) and publishing to both of the Marketplaces can look like this one here: https://github.com/KamasamaK/vscode-cfml/blob/master/.github/workflows/release.ymlwingrunr21 commentedon Jan 3, 2022
Thanks, as this project requires basically 2 extensions to be published (and I'm looking to wire it up to semantic release), I'll need to do some modifications.
filiptronicek commentedon Jan 3, 2022
Please do ping me if there is anything I can help with!