Publish GitLens in Open VSX

[tdemin]

There's an alternate open source extension marketplace for VSCode, Open VSX.

As Microsoft's extensions marketplace cannot be used by Code-OSS and VSCodium users for legal reasons, it's probably a good idea to make GitLens available to them there.

The process of publishing an extension at Open VSX is outlined here.

[orblazer]

This is published on vsx but @eamodio have not make auto update on this.

[tdemin]

@orblazer it's not published by @eamodio, see this text on the addon page:

The “GitLens — Git supercharged” extension was published by open-vsx. This user account is not related to the namespace eamodio of this extension

The version there is also severely outdated and is currently at 10.2.1. Mirroring extensions manually is no good, only the extension maintainers are able to actually keep stuff up to date.

[orblazer]

Yes but she have claim the namespace : https://github.com/eclipse/open-vsx.org/issues/9

[rob4226]

+1 Please add to Open VSX

[brianking]

fyi ... https://open-vsx.org/extension/eamodio/gitlens

However, it is It would be better for the owner to publish themselves. Please see why it is recommended.

This repo is to seed the registry with extensions when maintainers cannot, for instance because they work for MS, or not active anymore.

The docs for publishing the extension are here. Technically this should be straightforward. You get a token and call ovsx publish with it. For example, this is how RedHat publishes their java extension: redhat-developer/vscode-java@ff51dbf/Jenkinsfile#L73-L82

Let me know if you are open to a PR contributing a release GH action both to MS marketplace and OpenVSX, similar to PeterWone/vsc-print#121.

[GabrielPPavan]

Any news on this? Ive gotten early access to Google IDX and its lacking gitlens... I anticipate that when IDX launches for good, the demand for this will increase drastically...