Skip to content

Conversation

@zapta
Copy link

@zapta zapta commented Dec 26, 2025

  • [ X] 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).
  • [X ] This extension has an OSI-approved OSS license (we don't accept proprietary extensions in this repository)

Description

This PR adds the extension fpgawars.apio that is already published on the VSCode marketplace to the list of auto published extensions in the Eclipse market.

https://marketplace.visualstudio.com/items?itemName=fpgawars.apio

I am a co-author and signed the eclipse ECA.

@zapta
Copy link
Author

zapta commented Jan 17, 2026

Hello maintainers, anything we can do on our side to have this PR cleared for merging?

We submitted it here per a user complaint that the extension is not available on VSCodium.

@filiptronicek
Copy link
Collaborator

Hey there @zapta 👋
as per our contributing guidelines:

A goal of Open VSX is to have extension maintainers publish their extensions according to the documentation. The first step we recommend is to open an issue with the extension owner. 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.

The above also includes owners, who should publish the extension from their respective repositories instead of using this one, so that they own the publishing process from end to end and reduce the maintenance burden on this repository.

We also have a guide on doing this via GitHub actions, which you may find useful: https://github.com/EclipseFdn/publish-extensions/blob/master/docs/direct_publish_setup.md.

Let me know if you have any questions! I am happy to help

@zapta
Copy link
Author

zapta commented Jan 19, 2026

Hi @filiptronicek, thanks for looking into it.

Does it mean that will will need every future version of this app twice, once to Microsoft and once to you?

If the answer is yes, please reconsider allowing us to use this great automated publishing service here which will cut on our overhead. We are a non commercial team that run by volunteers.

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.

2 participants