microsoft / microsoft/winget-cli
Naming consistency for release artifacts
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
I'd like the naming of all the build artifacts to be consistent so I can automate the process of downloading and installing files.
Proposed technical implementation details
Ensure consistent naming for build artifacts so automation doesn't need to be modified.
Note: This is part of a larger effort to standardize internal build infrastructure and automation for build vs. deploy.
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 files, tests, or release entry points are named. Start by locating the build and release automation that produces the artifacts, then inventory their current names and the desired consistent convention; done means the build artifacts follow one naming scheme so download and installation automation does not need per-artifact changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100