-
Notifications
You must be signed in to change notification settings - Fork 10
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
Publication extension to Open VSX Registry #44
Comments
Hi, as a user of VSCodium I was about to request the same. Of the many extensions I use, scratchpads is the only one not in OpenVSX and still I go through the trouble of installing it manually because I find it super-useful 😄 . Note that it is possible to request OpenVSX to automatically mirror a package from the Microsoft Marketplace (this does not require any changes on this repo or any action on your side). @buenon, would consider requesting the auto-mirroring? ...or, alternatively, would you have any objection to me requesting the auto-mirroring myself? |
Hi guys, |
@mgerasimchuk @cpascual I published the extension on OpenVSX. In the process of claiming my namespace. Thanks again! |
@buenon thank you so much, I tested it right now on code-server, and it all works perfectly! |
Yes, thanks @buenon for your quick response! I confirm it is readily available from VSCodium now. Thanks a lot! |
Hi @buenon,
I would be happy to use your great extension in the popular VSCode IDE fork named ⭐ 69K code-server
By default the code-server only returns results from Open VSX. Microsoft Terms of Service does not allow programs other than those made by Microsoft to use the VSCode Marketplace. microsoft/vscode#31168 (comment)
According to the answer from code-server's maintainers, you need to publish your extension on https://open-vsx.org, by following this instruction - https://github.com/eclipse/openvsx/wiki/Publishing-Extensions and after this a lot of users of the code-server VSCode IDE will be able to use your extension
Thank you for your solution, and thank you in advance if you will publish it on OVSX
The text was updated successfully, but these errors were encountered: