microsoft / microsoft/winget-cli
Add support for agreements in PowerShell install flow
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
The PowerShell module doesn't appear to support the explicit agreements flow at the moment on the CLI.
winget install Microsoft.PowerAutomateDesktopwould require me to accept package agreements, but I could get around those by using:
Install-WinGetPackage -Id Microsoft.PowerAutomateDesktop
Proposed technical implementation details
No response
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 by comparing the winget install Microsoft.PowerAutomateDesktop flow with Install-WinGetPackage -Id Microsoft.PowerAutomateDesktop, focusing on how each handles package agreements. Trace the PowerShell module's install entry point and the corresponding CLI behavior; done means the PowerShell install flow supports explicit agreement handling consistently with the CLI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100