microsoft / microsoft/winget-cli

Add a flag/command to open a package's manifest in GitHub for review - perhaps `winget show --online`

Open
#1,459 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Feature
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

Similar motivation as in https://github.com/microsoft/winget-cli/issues/1458, when researching packages. Establishing trust. Etc. But instead of showing the manifest in my CLI, sometimes I want to see it online, especially if housed in source control (i.e. GitHub).

Then I can see who contributed to a given package. I can see when it was added, updated, etc. When major changes (if any happened). And why things are the way things are. Basically a way to see a manifest's history! Not just the current state as I proposed in https://github.com/microsoft/winget-cli/issues/1458

For this, it would rock to have a command or flag to open the manifest in the https://github.com/microsoft/winget-pkgs repository, or otherwise depending on the source. Of course this assumes it is possible for a given source.

As an example, when installing the Sono's Controller app, I might want to link to https://github.com/microsoft/winget-pkgs/blob/master/manifests/s/Sonos/Controller/13.0.0/Sonos.Controller.yaml

Description of the new feature/enhancement

We have winget show currently. We could have winget show --online to open a browser and load the respective manifest for the package/version/etc.

Proposed technical implementation details (optional)

This could be as simple as displaying a URL in the CLI output (in one or more commands) and then I can click it to open it as most terminals can handle that behavior easily. For example, at the end of all calls to winget show and other places that seem natural (perhaps a detailed list of search results could include a link per package found).

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 by tracing the existing winget show command and how it resolves a package, version, and source. Determine how a source can identify an online manifest, then define behavior for supported and unsupported sources. Done means the command or flag opens or displays the manifest URL for the selected package/version.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, github
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.