microsoft / microsoft/winget-cli

Potentially release Microsoft.WinGet.Client as a nuget package

Open
#4,322 0 comments 0 reactions 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

Description of the new feature / enhancement

This would be a potential way to fix this issue in PowerToys CommandNotFound feature

*Note this isn't a great idea really but would be a possible quick way to solve this issue

Proposed technical implementation details

As title mentions

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 reviewing the existing Microsoft.WinGet.Client surface and the linked PowerToys CommandNotFound issue. Define what releasing it as a NuGet package entails and verify that the package addresses that integration; this issue names no files or tests to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.