microsoft / microsoft/winget-pkgs
[New Feature]: Validate against duplicate monikers
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)
- 616
Description
### Description of the new feature/enhancement
* Related to https://github.com/microsoft/winget-pkgs/issues/16576
Manifest Validation in the pipelines should throw a warning when two different package identifiers share a moniker
### Proposed technical implementation details (optional)
_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
No file, test, or entry point is identified. Start by reviewing related issue microsoft/winget-pkgs#16576 and locating manifest validation in the pipelines; done means a warning is emitted when different package identifiers share a moniker.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100