Skip to content

Conversation

sapegin
Copy link

@sapegin sapegin commented Jun 26, 2025

  • I have read the note above about PRs contributing or fixing extensions
  • I have tried reaching out to the extension maintainers about publishing this extension to Open VSX (if not, please create an issue in the extension's repo using this template).
  • This extension has an OSI-approved OSS license (we don't accept proprietary extensions in this repository)

Description

Add all my VS Code extensions to the autopublish list.

@2zqa
Copy link
Contributor

2zqa commented Jul 23, 2025

These extensions are your own, right? If so, you should publish these extensions yourself using this guide: Publishing Extensions. Note there is a GitHub Action for this, mentioned at the bottom of the article.

@filiptronicek
Copy link
Member

Hey there @sapegin 👋
As @2zqa alluded to above, one of our main goals of Open VSX is to have extension maintainers publish their extensions according to the documentation1. The first step we recommend is to open an issue with the extension owner2. If the extension owner is unresponsive for some time, this repo (publish-extensions) can be used as a temporary workaround to ensure the extension is published to Open VSX.

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

Successfully merging this pull request may close these issues.

3 participants