microsoft / microsoft/winget-cli
WinGet Import acts as an alias for WinGet Configure
Open
Nobody has claimed this yet.
Command-Import
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
WinGet import should be able to run a packages.json file (the current output from winget export packages.json) or 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 reading the existing WinGet Import and WinGet Configure command entry points and how each input format is detected. Determine how the current packages.json export and WinGet Configuration file flows differ. Done means WinGet Import accepts and processes both formats while preserving existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100