microsoft / microsoft/PowerToys

CmdPal: recommend extension developers to to also add a winget package

Open Beginner friendly
#49,463 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Needs-Triage Product-Command Palette
Dominant language
C
Stars
139k
Forks
8.6k
PR merge metrics
PR metrics pending

Description

Description of the new feature / enhancement

The official documentation on how to publish an extension indicates the recommended way is to publish to the microsoft store.
As a result, most extension are only available via the store with no other way to install them.
The issue is many organisation disable access to the microsoft store, but winget still works as packages are usually hosted on github instead of a microsoft store server.
This results in a lot of extensions that I (and probably many other users) cannot use, all because of a single word on a web page.

Image

This page should be reworded to recommend publishing to both channels.
This is also inconistent with the Publish to Winget page that states publishing to winget is the recommended distribution method ...

Also please see #47076 and #38273 as it seems following these instructions produces installers that don't work with the command palette (extension not discovered).

Scenario when this would be used?

Any corporate network where access to the microsoft store servers are disabled

Supporting information

No response

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.

Research direction

Start with the linked Publish extension and Publish to Winget documentation pages and compare their distribution recommendations. Reword the extension publishing guidance to recommend both Microsoft Store and winget, while keeping it consistent with the winget page; verify that the related installation concerns in #47076 and #38273 are not contradicted.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.