microsoft / microsoft/winget-pkgs
[New Feature]: Wingetbot should update and remove in a single PR
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
Description of the new feature/enhancement
Have wingetbot create the new version and the old version in a single PR to reduce the number of pipeline runs.
Additionally, it would be easier if it was all one commit - since if there was an error maintainers can cherry-pick the commit and edit it rather than having to checkout the entire branch
Proposed technical implementation details (optional)
Example where wingetbot made multiple PRs:
- https://github.com/microsoft/winget-pkgs/pull/54941
- https://github.com/microsoft/winget-pkgs/pull/54940
Example where maintainers do the same thing in a single commit:
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
No files, tests, or entry points are named. Start by locating the wingetbot implementation that creates version-update pull requests and trace how it handles old and new versions; done means one PR and one commit contain both changes and reduce duplicate pipeline runs.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100