PowerShell lint (PSScriptAnalyzer over examples/**/*.ps1) currently lives as a somewhat isolated job in Extended Verification (verify-extended.yml), which is workflow_dispatch-only. As a result, .ps1 regressions surface late — e.g. in #22 a PSUseUsingScopeModifierInNewRunspaces failure only appeared on a manual Extended Verification dispatch, not in normal PR CI.
Possible direction
- A dedicated Windows/PowerShell workflow
- triggered primarily by
*.ps1 changes (paths: filter)
- reusable from Extended Verification (so the dispatch path still covers it)
That would surface PowerShell regressions much earlier while keeping Extended Verification focused on higher-level validation.
Follow-up from #22 (item C in the review comment).
PowerShell lint (PSScriptAnalyzer over
examples/**/*.ps1) currently lives as a somewhat isolated job in Extended Verification (verify-extended.yml), which isworkflow_dispatch-only. As a result,.ps1regressions surface late — e.g. in #22 aPSUseUsingScopeModifierInNewRunspacesfailure only appeared on a manual Extended Verification dispatch, not in normal PR CI.Possible direction
*.ps1changes (paths:filter)That would surface PowerShell regressions much earlier while keeping Extended Verification focused on higher-level validation.
Follow-up from #22 (item C in the review comment).