microsoft / microsoft/winget-pkgs
Merge mostly-duplicate packages: Voiden.Voiden / VoidenHQ.Voiden
Open
Nobody has claimed this yet.
Needs-Triage
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 616
Description
At the time of writing, there are 2 different packages for Voiden version 2.2.2:
- https://github.com/microsoft/winget-pkgs/blob/master/manifests/v/VoidenHQ/Voiden/2.2.2/VoidenHQ.Voiden.installer.yaml
- https://github.com/microsoft/winget-pkgs/blob/master/manifests/v/Voiden/Voiden/2.2.2/Voiden.Voiden.installer.yaml
The 2 packages do however have sharply differing metadata in their manifests, so the process to merge the 2 packages would be harder than usual.
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
Compare the two referenced Voiden 2.2.2 installer manifests at manifests/v/VoidenHQ/Voiden/2.2.2/VoidenHQ.Voiden.installer.yaml and manifests/v/Voiden/Voiden/2.2.2/Voiden.Voiden.installer.yaml. Review the differing metadata and determine the repository’s expected merged representation. Done means the duplicate package entries are consolidated without losing correct metadata.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100