microsoft / microsoft/winget-studio
Add support for WinGet REST sources
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 67
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Description of the new feature / enhancement
This would be a perfect place to have a GUI to help deploy/manage private WinGet REST sources.
I'd like to be able to "source" packages from the WinGet community repository and or the Microsoft Store source.
Then the tool could help upload the installer to the approved enterprise location for binaries (Azure Storage, ACR, etc...) and modify the manifest appropriately and publish it to the private REST source.
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
The issue names no files, tests, or entry points; start by mapping the existing GUI and WinGet REST-source handling before deciding where this feature belongs. Done would cover sourcing community or Microsoft Store packages, uploading installers to an approved enterprise location such as Azure Storage or ACR, updating manifests, and publishing to a private REST source.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- cloud, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100