microsoft / microsoft/winget-create
"wingetcreate new" with private bits
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 651
- Forks
- 114
- Avg merge
- 7h 52m
- Merged PRs (30d)
- 3
Description
Brief description of your issue
Getting ready to release a package to winget, there is no way to provide Authorization and Accept headers to WinGetCreate's commands, such as "new".
I'm getting ready to release an app, but its on my private github. I have a PAT, and with proper auth I want to be able to get ready to release the app, generating the manifest from the new command.
It can be a simple parameter provided as environment variables to the internal HttpClietn from PackageParser.
Steps to reproduce
wingetcreate new
Provide url to private github release.
Expected behavior
Given proper environment variable setup, I can generate a manifest by pointing to a URL that requires auth.
Actual behavior
Fails with 404.
Environment
v1.10.3.0
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 at the "new" command and the PackageParser HTTP client mentioned in the issue; inspect how the private GitHub release URL is fetched and how environment variables could supply Authorization and Accept headers. Done means "wingetcreate new" can generate a manifest from an authenticated private release URL instead of failing with 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github
- Domain
- authentication, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100