microsoft / microsoft/winget-pkgs
[New Feature]: Allow packages submitted by `Verified Publishers` to be automatically merged
Open
Nobody has claimed this yet.
Area-Validation-Pipeline
Issue-Feature
- 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
When certain conditions are met, allow automatic merge of PRs.
This would be somewhat-analogue to add moderators but restricted for specific packages.
Proposed technical implementation details (optional)
Possible rules:
- If the software vendor is pushing a new version, automatically merge the PR.
- Could exist as an explicit whitelist text file:
UserA --can add packages for manifest--> PackageId.1- Whitelists can be protected by CODEOWNERS or similar.
- For packages hosted on GitHub, it could be inferred either:
- from Manifest Id. IE: Manifest id
UserA.packageBcan be updated by userUserA - from download url:
github.com/user/repo/releases/....
- from Manifest Id. IE: Manifest id
- Could exist as an explicit whitelist text file:
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 implementation files or tests are identified. Start by locating the pull-request automation, manifest ownership rules, and any existing CODEOWNERS or whitelist configuration; done requires an agreed rule set for verified publishers and package-specific automatic merges.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100