Dev Home Feature Exploration: Detect a configuration file when cloning a repo #2211
Description
Please Provide Feedback & Ideas!
Please let us know what you think about this feature by commenting on this issue! We'd love to hear your ideas and feedback!
Let us know:
- What do you like about the feature?
- What do you think is missing / what could improve the experience?
Overview
This issue outlines the proposed experience for detecting configuration files in repos that are being cloned as part of the machine configuration end to end flow. Once the configuration files have been detected, allow the user to review, approve, and add the configuration files to the set up process to fully configure the machine to be ready for development.
The Problem
Many repositories have a set of required tools or settings that need to be installed or enabled in order to build the project. As Winget Configuration files make it easier to set up those repos in one go, we want to add the detection and running of a configuration file into the machine configuration flow to make it easier to be that much closer to development.
Scenarios
| # | Scenarios |
|---|---|
| 1 | As a user, I want to know when a repository I clone has a Winget Configuration file available so that I can set up that repository for development. |
| 2 | As a user, I want to be able to review and approve each configuration file before it is added to the queue for set up so that I can be confident in what is being configured on my machine. |
| 3 | As a user, I want to be able to see the list of all of the configuration files detected, whether or not they ran, on the summary page after setting up so that I can view their file location or run them individually in a separate flow |