Kelly Michels 32e8d7430f chore(ci): add a GitHub Actions workflow that lints with PSScriptAnalyzer and runs the Pester suite on Windows (#74) ... * chore(ci): run the Pester suite on push and pull request This repo is one of the twelve on the fleet board and had no CI at all, so the only thing ever running these tests was one workstation at 04:00 - and on 2026-09-09 that run did not happen, which is how the gap surfaced. windows-latest rather than ubuntu: Pester runs on Linux, but these scripts deploy from a Windows workstation and the suite reads like it. Proving them on Linux would prove something nobody runs. Pester pinned to 5.x, since the suite uses the v5 configuration API and the Windows image carries a v3 that would otherwise be picked first, and -CI so a red suite fails the job - Invoke-Pester on its own exits 0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * chore(ci): lint with PSScriptAnalyzer before the Pester suite PSScriptAnalyzer is the PowerShell linter, and there is no typecheck for PowerShell, so it is the whole of that half. Errors fail the job; warnings are printed and do not - the repo was written without the analyzer, and a gate that goes red on day one over style becomes a gate someone disables. PSAvoidUsingWriteHost is excluded outright: these are command-line tools whose Write-Host output is the interface. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>		2026-09-09 17:53:16 -05:00
..
tests.yml	chore(ci): add a GitHub Actions workflow that lints with PSScriptAnalyzer and runs the Pester suite on Windows (#74)	2026-09-09 17:53:16 -05:00