microsoft / microsoft/winget-pkgs
[FR] Automated testing - MSI detection GUID
Open
Nobody has claimed this yet.
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
Before a new MSI package is added to the manifest, it would be great if the provided detection MSI GUID is validated somehow.
Example problem:
Example solution (correcting the GUID):
Proposed technical implementation details (optional)
Download the MSI, get the GUID using a tool like Orca or lessmsi maybe?
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 linked issue comment and pull request to understand the incorrect detection GUID and its correction. Then locate the manifest validation workflow in this repository; done means a new MSI manifest's detection GUID is checked against the package before it is added.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100