-
Notifications
You must be signed in to change notification settings - Fork 16
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
Publish batch-rename to Open VSX #8
Comments
3 tasks
I tried to publish it using their automatic pipeline. However, there are some build errors that I fixed in this PR. |
This extension is now published: https://open-vsx.org/extension/JannisX11/batch-rename-extension |
@omhomurlu now that the extension has been published, should this issue be closed? |
Yes, thank you!
…On Sun 29 Sept 2024, 15:24 Karl Horky, ***@***.***> wrote:
@omhomurlu <https://github.com/omhomurlu> now that the extension has been
published, should this issue be closed?
—
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUCIISYYBLZ2YVAV7Z3DPMTZY75P7AVCNFSM6AAAAABPBW4BOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBRGM2TMNRSHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Ok, great, if you or @JannisX11 could close it, then that would be good 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.The text was updated successfully, but these errors were encountered: