PowerShell / PowerShell/PSScriptAnalyzer
Rule to ensure that `ConfirmImpact=High` has `Confirm` and `-Force`
Open
Nobody has claimed this yet.
Issue - New Rule
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Per PowerShell/PowerShell#3337, whenever ConfirmImpact=High is specified, we should suggest having a -Confirm and -Force parameter to ensure that users can skip the prompt in non-interactive scenarios.
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
No implementation files, tests, or entry points are named. Start by reading the referenced PowerShell/PowerShell#3337 issue and then inspect how PSScriptAnalyzer represents existing rules; done means a rule identifies high-impact confirmations that lack both -Confirm and -Force handling, with coverage for the intended cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- devtools, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100