Ability to specify dependency targets to skip at the CLI
- Dominant language
- C#
- Stars
- 4.2k
- Forks
- 778
- Avg merge
- 1h 15m
- Merged PRs (30d)
- 19
Description
There are often times where I am developing a task at the end of a list of targets. During this temporary development I want to run the target frequently without running the targets it depends on.
Naturally I comment out the `.IsDependentOn` for the task under development. However I'd strongly prefer to be able to specify `-Target X -SkipTarget Y -SkipTarget Z` or something similar. I don't want to make any changes to the file on account of temporary development. This way I can commit as I make progress without forgetting to uncomment and recomment.
I'd also prefer not to build a hierarchy where `Release` depends on `Test` and `ReleaseWithoutTest` or introduce environment variables or any other kind of script boilerplate just for the sake of being able to temporarily skip a given target.
Contributor guide
Research direction
Start by tracing how the CLI parses repeated target options and how target dependencies are selected for execution. Define the behavior for multiple skip-target values, including their effect on dependencies, then add or update tests for command-line parsing and dependency execution. Done means a target can be run while named dependency targets are skipped without editing the build script.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100