microsoft / microsoft/winget-pkgs
[Update Request]: Move Google Chrome MSI to https://github.com/microsoft/winget-pkgs/tree/master/manifests/g/Google/Chrome/MSI
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
What type of update are you requesting?
A change to the package metadata
Current Package Identifier
Google.Chrome
Package Version
131.0.6778.205
Please describe the changes you would like to see
- Move version
This one https://github.com/microsoft/winget-pkgs/tree/master/manifests/g/Google/Chrome/131.0.6778.205
should moved to a separate directory similar to:
https://github.com/microsoft/winget-pkgs/tree/master/manifests/g/Google/Chrome/EXE
- Create Directory MSI
suggestion: https://github.com/microsoft/winget-pkgs/tree/master/manifests/g/Google/Chrome/**MSI**
- change PackageIdentifier
And the PackageIdentifier should be changed from Google.Chrome to Google.Chrome**.MSI**
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 with the manifests under manifests/g/Google/Chrome/131.0.6778.205 and compare them with manifests/g/Google/Chrome/EXE. Review how the repository organizes package identifiers and directories, then move the requested version into an MSI directory and update its identifier to Google.Chrome.MSI. Done means the metadata is located under the requested path with the new identifier and remains consistent with the existing EXE layout.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100