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
Is your feature request related to a problem? Please describe.
Afaict it's not possible to use this extension on Gitpod.
Describe the solution you'd like
I'd like to be able to install this extension in a Gitpod workspace
Describe alternatives you've considered
Not using Gitpod...which maybe I will because I really like this extension!
Additional context
I wrote up a similar request on the cfn-lint extension's repository just now, so I'll copy what I wrote there below:
Just learned that only extensions published to the OpenVSX registry will work on Gitpod, and was curious if the maintainers of this repo would be interested in publishing there as well.
The steps for doing so are listed here. 1-4 have to do with setting up an account and generating a token, then the last step discusses how to actually perform the publish.
It seems like updating the Github workflow publish pipeline to also publish to OpenVSX could look something like this.
The text was updated successfully, but these errors were encountered:
Thank you for opening this request @Grunet and supplying the neccesary information. This should be an easy fix from my end indeed, I'll pick it up if I got some time soon!
Is your feature request related to a problem? Please describe.
Afaict it's not possible to use this extension on Gitpod.
Describe the solution you'd like
I'd like to be able to install this extension in a Gitpod workspace
Describe alternatives you've considered
Not using Gitpod...which maybe I will because I really like this extension!
Additional context
I wrote up a similar request on the cfn-lint extension's repository just now, so I'll copy what I wrote there below:
Just learned that only extensions published to the OpenVSX registry will work on Gitpod, and was curious if the maintainers of this repo would be interested in publishing there as well.
The steps for doing so are listed here. 1-4 have to do with setting up an account and generating a token, then the last step discusses how to actually perform the publish.
It seems like updating the Github workflow publish pipeline to also publish to OpenVSX could look something like this.
The text was updated successfully, but these errors were encountered: