microsoft / microsoft/winget-pkgs
[New Feature]: Possible Duplicate Detection
Nobody has claimed this yet.
- 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
When a new package is submitted and it has the same name as another "known" package, the PR should be flagged for review to make sure the submission is appropriate.
We check for SHA256 duplicates.
We should consider adding "name", productCode, and upgradeCode
Reference:
* https://github.com/microsoft/winget-pkgs/pull/345805
### 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
Start by reviewing the referenced pull request 345805 and the existing SHA256 duplicate checks. Determine where package submissions are flagged for review, then define completion as detecting matching name, productCode, and upgradeCode values for new packages.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100