Let users define their own levels (or extend existing ones) in the config file hierarchy. A team could define a ci level that's standard plus project-specific patterns, referenced by name in pipelines instead of repeating -IncludeFilePattern lists. The config system already supports the merge semantics
Let users define their own levels (or extend existing ones) in the config file hierarchy. A team could define a ci level that's standard plus project-specific patterns, referenced by name in pipelines instead of repeating -IncludeFilePattern lists. The config system already supports the merge semantics