microsoft / microsoft/winget-cli
Add support for WinGet Export and WinGet Import in PowerShell module.
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
I want to be able to leverage WinGet Import and WinGet Export via PowerShell.
There is presently an Export-WinGetPackage cmdlet that is equivalent to the WinGet Download functionality, so we will need to ensure we have an appropriately named (and hopefully not confusing) pair of cmdlets for this functionality.
[!NOTE]
The current WinGet Impoart and WinGet Export functionality generates a JSON based file containing the list of applications associated with sources rather than the YAML syntax for a WinGet Configuration File.
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 locating the PowerShell module and the existing Export-WinGetPackage cmdlet, then trace how it maps to WinGet Download. Review the current WinGet Import and Export behavior and its JSON package-list format; the work is done when appropriately named PowerShell cmdlets expose both operations without confusing them with download or WinGet Configuration YAML functionality.
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
- Needs clarification
- Newbie friendliness
- 35/100