microsoft / microsoft/winget-cli
Add wingver command with ASCII branding (similar to neofetch)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Relevant area(s)
WinGet CLI
Description of the new feature / enhancement
I propose adding a new command (or an alias) like wingver that displays the current WinGet version alongside a stylish ASCII art logo of the Windows Package Manager.The concept:In many Linux environments, tools have "branded" version outputs. Instead of just a plain number like v1.8.1911, running wingver should display:An ASCII art logo of WinGet (the stylized "W" or the package icon).System info summary: OS Version, WinGet version, and CPU architecture.Example of how it could look:
Why it's cool:Branding: It gives WinGet a recognizable visual identity in the terminal.User Experience: It's much more satisfying to see a "pro" status screen than a single line of text.Ease of access: wingver is short and easy to remember for debugging and sharing environment info.
And one more idea. Add Shortcut Support (e.g., Ctrl + Alt + T)I suggest adding hotkey support for quicker interactions. For example, using Ctrl + Alt + T to quickly trigger a specific action, such as opening a "Top/Trending" packages view or instantly focusing the search bar in the terminal. This would bring a more "pro-user" desktop experience to the CLI.
Proposed technical implementation details
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
No files, tests, or command entry points are named; start by locating the WinGet CLI's existing version command and command-registration path. Clarify whether the deliverable is the wingver output, the unrelated shortcut support, or both, then define the supported system fields and a testable output before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100