Fix typos and formatting#443
Conversation
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 9452aeb: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Updates the Invoke-ScriptAnalyzer reference documentation to improve readability and consistency, primarily via formatting and example adjustments.
Changes:
- Reformatted several examples to use splatting for improved readability.
- Cleaned up example output formatting and standardized
$PSHOMEcasing in examples. - Updated the
-Severityparameter section (including addingParseError) and refreshedms.date.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| The parameter filters the rules violations only after running all rules, regardless of severity. To | ||
| filter rules efficiently, use `Get-ScriptAnalyzerRule` to select the rules you want to run. |
PR Summary
Fix typos and formatting
PR Checklist