microsoft / microsoft/winget-pkgs
Mods should be given write access to wingetbot's PRs
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
@denelon I would like to add that moderators should be given write access to @wingetbot's PRs. It really hurts for someone to open a new, fresh PR with the "changes requested" on the @wingetbot's PR.
Example - https://github.com/microsoft/winget-pkgs/pull/35336 opened by @wingetbot, Levvie requested changes. Now, another person has to open another PR for the same package with suggestions applied (https://github.com/microsoft/winget-pkgs/pull/35351).
I think you can add the mods team as a collaborator on https://github.com/wingetbot/winget-pkgs
Originally posted by @vedantmgoyal2009 in https://github.com/microsoft/winget-pkgs/issues/30364#issuecomment-973979365
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
Review the linked wingetbot/winget-pkgs repository and the example pull requests 35336 and 35351 to understand the requested workflow. Done means moderators can apply requested changes to wingetbot's PRs without opening a replacement PR, subject to the appropriate repository permissions.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100