We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
Not sure if you're aware but there's also an independent, open source, extensions registry called Open VSX
It's used for OSS builds of vs-code that aren't allowed to use Microsoft's solution due to the license of their VS Code builds. (eg. VSCodium)
Their docs are great for publishing extensions.
It would be great if you could publish this extension there as part of your release process.
I would be happy to help out in this regard if needs be. I have recently published a fork of the Visual studio Keymap extension.,
The text was updated successfully, but these errors were encountered:
This would be helpful for everyone who runs one of the many forks of vscode.
Sorry, something went wrong.
No branches or pull requests
Hi,
Not sure if you're aware but there's also an independent, open source, extensions registry called Open VSX
It's used for OSS builds of vs-code that aren't allowed to use Microsoft's solution due to the license of their VS Code builds. (eg. VSCodium)
Their docs are great for publishing extensions.
It would be great if you could publish this extension there as part of your release process.
I would be happy to help out in this regard if needs be. I have recently published a fork of the Visual studio Keymap extension.,
The text was updated successfully, but these errors were encountered: