microsoft / microsoft/WindowsDeveloperConfig
Detect previously applied steps to skip, speeding up later runs for troubleshooting or update
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 2.2k
- Forks
- 168
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 5
Description
As an idempotent system, having to rerun to correct failures or perform updates should be fast.
It appears that reruns are attempting to run all items over again. To reduce time and friction, it would be a good idea to store a version/release number to check for new functionality or updates to existing, and run a check for the configuration before attempting to apply it, then skip those that are present and on the latest changeset.
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
The issue does not name files, tests, or an entry point. Start by tracing how configuration items are applied during a rerun and determine how their versions or changesets can be recorded and checked. Done means reruns skip items already present at the latest changeset while still applying new or updated functionality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100