Skip to content

[Freshness] PSScriptAnalyzer Article Updates - Batch 14#417

Open
Xelu86 wants to merge 3 commits into
MicrosoftDocs:mainfrom
Xelu86:UBatch
Open

[Freshness] PSScriptAnalyzer Article Updates - Batch 14#417
Xelu86 wants to merge 3 commits into
MicrosoftDocs:mainfrom
Xelu86:UBatch

Conversation

@Xelu86

@Xelu86 Xelu86 commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

PR Summary

These updates target the following PSScriptAnalyzer articles:

  • UseSingleValueFromPipelineParameter
  • UseSingularNouns
  • UseSupportsShouldProcess
  • UseToExportFieldsInManifest
  • UseUsingScopeModifierInNewRunspaces
  • UseUTF8EncodingForHelpFile

Fixes: AB#582013
Fixes: AB#582014
Fixes: AB#582015
Fixes: AB#582016
Fixes: AB#582017
Fixes: AB#582018

PR Checklist

  • Descriptive Title: This PR's title is a synopsis of the changes it proposes.
  • Summary: This PR's summary describes the scope and intent of the change.
  • Contributor's Guide: I have read the contributors guide.
  • Style: This PR adheres to the style guide.

Copilot AI review requested due to automatic review settings June 11, 2026 19:11

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates several PSScriptAnalyzer rule reference docs to use clearer, more consistent descriptions and examples.

Changes:

  • Reworded rule descriptions and standardized “Noncompliant/Compliant” example headings.
  • Added/expanded examples (notably for UTF-8 help file encoding).
  • Updated metadata (descriptions and ms.date) and refreshed/standardized links.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 5 comments.

Show a summary per file
File Description
reference/docs-conceptual/PSScriptAnalyzer/Rules/UseUsingScopeModifierInNewRunspaces.md Clarifies the rule’s intent and simplifies examples/wording.
reference/docs-conceptual/PSScriptAnalyzer/Rules/UseUTF8EncodingForHelpFile.md Expands guidance and adds compliant/noncompliant examples; updates links.
reference/docs-conceptual/PSScriptAnalyzer/Rules/UseToExportFieldsInManifest.md Rewords description and simplifies examples around export fields.
reference/docs-conceptual/PSScriptAnalyzer/Rules/UseSupportsShouldProcess.md Rephrases description and standardizes section headings.
reference/docs-conceptual/PSScriptAnalyzer/Rules/UseSingularNouns.md Rewords description, reorganizes config/parameters, standardizes examples.
reference/docs-conceptual/PSScriptAnalyzer/Rules/UseSingleValueFromPipelineParameter.md Rewords description and improves notes punctuation/clarity.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread reference/docs-conceptual/PSScriptAnalyzer/Rules/UseToExportFieldsInManifest.md Outdated
Comment thread reference/docs-conceptual/PSScriptAnalyzer/Rules/UseToExportFieldsInManifest.md Outdated
Comment thread reference/docs-conceptual/PSScriptAnalyzer/Rules/UseSingularNouns.md Outdated
@learn-build-service-prod

Copy link
Copy Markdown

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown

@learn-build-service-prod

Copy link
Copy Markdown

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants