VSpaceCode is missing from the Open VSX registry about vscode-which-key HOT 12 CLOSED

Really happy that VSCodium users can use our extensions. Thanks again Steven :)

from vscode-which-key.

New version is released. https://open-vsx.org/extension/VSpaceCode/whichkey

from vscode-which-key.

Furthermore, this extension has no a "deploy" action like VSpaceCode, this might be a good time to add it.

I've been deploying manually. I will add an action and a token just like VSpaceCode for this repo tomorrow so it has deploy action to MS registry like VSpaceCode. We need more discussion in moving forward with open VSX, see below.

As far as supporting extra registry, I am supportive of it, and I hope it won't end up being supporting multiple registries due to possible fragmentations.

A tidbit about Open VSX: when I tried to register/log in, it requires a github account, and reading of the profile. There isn't a email option as far as I know. It seems like we are registering/giving access our our profile to TypeFox, a company in Germany. I am not sure if I personally want to register for it.

As far as deployment goes, there is an action that supports deploying to all registries https://github.com/HaaLeo/publish-vscode-extension. It seems to contain more code than the one we are using, probably need to take a look.

Another note: I can see a potentially problem where the extensions we bundled in VSpaceCode are not on the registry. I guess the worst case is that they just won't be able to use some commands unless they install the missing extension. For which-key, it is fine because it is designed to be standalone.

from vscode-which-key.

I added automatic deployment on vscode-which-key just like the one on VSpaceCode on 8104b93

from vscode-which-key.

Let's wait until they transition to Eclipse Foundation. https://blogs.eclipse.org/post/brian-king/open-vsx-registry-under-new-management

from vscode-which-key.

Just an update. I signed up with my github account and claimed the VSpaceCode namespace. I also updated the github action, which means the next version will be deployed to both vs marketplace and open-vsx

@MarcoIeni I can add you in as another owner to the namespace in open-vsx once you are signed up with you github account. Let me know if you want to do that.

from vscode-which-key.

If you want to do it, it would be great! This should be integrated with the GitHub Deploy Action.
As an action to deploy the extension we are using this one, but I don't see an option to update to the Open VSX registry, too.
The documentation you linked suggest another action. For me we can do the transition to that one if it is compatible with both.
Furthermore, this extension has no a "deploy" action like VSpaceCode, this might be a good time to add it.

Anyway, one of the maintainers has to setup the token, right?

Side note: this issue is good for both the vspacecode-which-key (this repo) and VSpaceCode extension.
We can keep the discussion here for both I think.

from vscode-which-key.

hi all! any updates here? i'd like to try VSpaceCode on vscodium :)
can't find that nor vscode-which-key on the marketplace!

from vscode-which-key.

That's great Steven, thanks!

On which website should I sign in?

from vscode-which-key.

You can sign in with you github account on https://open-vsx.org

from vscode-which-key.

done

from vscode-which-key.

added :)

from vscode-which-key.