-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please consider publishing this in the Open VSX Registry #5
Comments
Alternatively, I'm happy to publish it for you, if that won't be an issue. There's a lot of open source VS code alternatives out there that can't use the MS extension store, most of them use VSX and it just needs to be setup once (about 10 mins). |
Bump to see if this can be published on OpenVSX or can @CarterQC have permission to do so? |
Any updates to this? :) It's the only way to use the extension in Gitpod.io. |
Made a fork and published to Open VSX Registry (https://open-vsx.org/extension/victorbjorklund/phoenix). Happy to remove it when/if the official version if published. |
I could help with publishing as well. As long as the team is willing to publish to Open VSX. |
More info regarding the legal issues of using the ms marketplace outside of vscode: microsoft/vscode#31168 @victorbjorklund Please merge the open pull-request (victorbjorklund#1) and publish the update to OpenVSX - thanks! ;) |
To allow the use of this extension in open source VS Code alternatives, please consider registering this on https://open-vsx.org/
There are instructions on how to do that here: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions
Thanks!
The text was updated successfully, but these errors were encountered: