microsoft / microsoft/winget-create
Automation targeted improvements
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 651
- Forks
- 114
- Avg merge
- 7h 52m
- Merged PRs (30d)
- 3
Description
Description of the new feature / enhancement
Improve error reporting from exceptions: currently the internal GH exceptions are lost so it is difficult to know if they are transient, rate limits, etc. Maybe just a --verbose would be good enough here to log exception stacks when they would otherwise be converted to a user message.
Improve retry logic (with backoff) so that transient errors are less impactful in automation scenarios. For example, when attempting to create the PR, it would be better to try a few times before giving the user an error to have them take over. This is true all of the time, but especially in automation where the only recourse is to run the pipeline again.
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 tracing how internal GitHub exceptions are converted into user messages and how pull request creation handles failures. Define completion as retaining exception details for verbose output and retrying transient failures with backoff before reporting an error, especially in automation scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100