Build a WinGet Configuration for this project

[denelon]

Code of Conduct

• I agree to follow this project's Code of Conduct

What would you like to see added?

I'd love to have a WinGet configuration file in this project so it's easier for me as a developer on Windows to contribute to oh-my-posh.

The configuration file convention is to place a "configuration.dsc.yaml" file in a ".configurations" directory in the root of the project. If this is done, when the project is cloned using Dev Home, the user will be prompted to run the configuration which should install the tools necessary to build the project. In some cases, it may make sense to have more than one configuration file based on user preference for different IDEs or toolchains.

Samples:

• Dev Home
• PowerToys
• WinGet CLI

Note: If Visual Studio is used, there should be a configuration per SKU so users who already have a specific SKU installed don't end up with another installation. That's why there is more than one file in the PowerToys repository.

As an early adopter, don't hesitate to reach out to me directly for help in either finding DSC Resources, or with any challenges encountered.

Generally, the goal would be that a user could run the configuration and immediately they are ready to build/compile the project. This should eliminate the toil involved in trying to figure out how to get a Windows device set up properly to contribute to this project.

[github-actions]

This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues.
If you have found a problem that seems similar, please open a discussion first, complete the body with all the details necessary to reproduce, and mention this issue as reference.