PowerShell / PowerShell/vscode-powershell
Publish to OpenVSIX Registry
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
[Requested by @jpsnover]
We should publish to OpenVSIX registry as well for vscode forks and other tools to be able to utilize PowerShell.
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- powershell, typescript
- Domain
- ci-cd, documentation, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100