PowerShell / PowerShell/PSScriptAnalyzer
Switch to elevate warning to errors
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Summary of the new feature
As a user, I want a single switch to elevate warnings to errors so that my repos can have error-less, warning-less code. In CI scenarios, like @justinGrote's Super-Duper-Linter I need the task to fail when there are only warnings.
Proposed technical implementation details (optional)
@rjmholt mentioned the -NoExit param but I'm not sure if that will exit on warnings as well...
What is the latest version of PSScriptAnalyzer at the point of writing
1.19
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
Start with the linked Invoke-ScriptAnalyzer documentation for the -NoExit parameter and the issue's requested CI behavior. Determine how warnings are currently reported and define completion as a single switch that makes warning-only analysis fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100