Skip to content
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 to OpenVSX #1

Open
yorickpeterse opened this issue Mar 15, 2023 · 2 comments
Open

Publish to OpenVSX #1

yorickpeterse opened this issue Mar 15, 2023 · 2 comments

Comments

@yorickpeterse
Copy link
Contributor

Original issue on GitLab: https://gitlab.com/inko-lang/vscode/-/issues/1

This is just a tiny feature request. Forks of vscode don't use the official Microsoft marketplace for extensions, but instead use Open VXS.

The extension should probably also be published there, to reach more people. (This should only require making an account and sending it there, no changes to the actually extension.)

I don't know for how many people this is relevant, but some on some linux distributions the default package of vs code uses Open VSX.

@roetlich
Copy link

roetlich commented Jul 10, 2023

FYI, this is how I did pushing to Open VXS and the MS one 2 years ago: https://github.com/roetlich/pointless-syntax-highlighting-vscode/blob/master/.github/workflows/publish.yaml

Not sure if this still works, but probably 😅
Still requires regenerating the MS token every now and then, but at least openvsx should just work automatically. If you want to I can look into it, but I can't create the token.

@yorickpeterse
Copy link
Contributor Author

@roetlich Do you know if it's possible to automate the token regeneration process? If so that would be pretty neat, and we could automate the whole process, but my guess is that this isn't possible 😞

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants