Publish to OpenVSIX Registry

Open
#5,470 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
powershell, typescript
Domain
ci-cd, documentation, release

Research direction

Start with docs/azure_data_studio/README_FOR_MARKETPLACE.md, especially the linked lines 58-67, and review the existing CI pipeline. Confirm legal and pipeline feasibility with maintainers, update the README with best-effort support for VS Code forks and other OpenVSIX consumers, and publish the package once approved.

Written by the indexing model from the issue text.

Description

Area-Build Release Issue-Enhancement Needs: Maintainer Attention

[Requested by @jpsnover]

We should publish to OpenVSIX registry as well for vscode forks and other tools to be able to utilize PowerShell.

https://github.com/PowerShell/vscode-powershell/blob/01e8ef8605b6602e1f1fa935855de1a62d70a7ac/docs/azure_data_studio/README_FOR_MARKETPLACE.md?plain=1#L58-L67

Tasks

  • Verify legal feasibility

  • Verify CI pipeline feasibility

  • Update README to clarify best-effort support for vscode forks and other OpenVSIX Consumers

  • Publish Package

@andyleejordan can you verify the MS legal feasibility of this? You'd probably have to own the devops pipeline work as well.

Dominant language
TypeScript
Stars
1.9k
Forks
548
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PowerShell/vscode-powershell

All issues in PowerShell/vscode-powershell

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.