Skip to content

⚙️ [Maintenance]: PowerShell guidance scripts are centrally available - #508

Draft
Marius Storhaug (MariusStorhaug) wants to merge 2 commits into
mainfrom
import-guidance-scripts
Draft

⚙️ [Maintenance]: PowerShell guidance scripts are centrally available#508
Marius Storhaug (MariusStorhaug) wants to merge 2 commits into
mainfrom
import-guidance-scripts

Conversation

@MariusStorhaug

@MariusStorhaugMarius Storhaug (MariusStorhaug) commented Aug 9, 2026

Copy link
Copy Markdown
Member

Maintainers can now find the published PowerShell guidance examples alongside Process-PSModule, giving the framework a single maintained home for the scripts that explain common implementation patterns.

New: Published PowerShell guidance scripts

The repository now carries the complete current set of guidance scripts for collections, strings, call stacks, pipeline execution, module loading, file access, and web calls. The published documentation includes the purpose of every script and links directly to the tracked directory. These are reference examples; run an individual script only when its scenario is appropriate for the local environment.


Technical details

-Imported the 14 current guidance/ Git blobs from PSModule/docs without changing their contents and verified every imported blob ID against the source repository.
-Added a scoped .gitattributes rule so the imported source stays LF-normalized in Git on Windows checkouts.
-Added the guidance-script reference page, Reference landing-page entry, and site navigation entry. guidance/ remains outside src/ because these scripts are framework reference assets, not Process-PSModule module source; no manifest wiring is required.
-Implementation plan progress: source import and published discoverability are complete.
-Issue convergence sweep: searched open guidance-related issues. PSModule/Process-PSModule#423 is related documentation-consolidation context but is not fully satisfied by this import; no issue is closed.
-Strict documentation validation exposes 28 pre-existing migrated-link warnings outside this diff; the normal build generates the new guidance page successfully. The bounded follow-up is PSModule/Process-PSModule#509.

Changed surfaceStandards checkedFramework docs checkedResult
guidance/** (PowerShell)PowerShell syntax parsing, source fidelityRepository layout and module source layoutAligned
docs/content/**, docs/zensical.tomlMarkdown structure and navigationDocumentation publishingAligned; strict baseline tracked in #509
.gitattributesRepository text normalizationRepository standardAligned
Relevant issues (or links)

-No scoped delivery issue was provided; this import was requested directly.
-#423
-#509

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown

Super-linter summary

LanguageValidation result
CHECKOVPass ✅
CSSPass ✅
CSS_PRETTIERPass ✅
GITHUB_ACTIONSPass ✅
GITHUB_ACTIONS_ZIZMORPass ✅
GITLEAKSPass ✅
GIT_MERGE_CONFLICT_MARKERSPass ✅
HTMLPass ✅
JAVASCRIPT_ESPass ✅
JAVASCRIPT_PRETTIERPass ✅
MARKDOWNPass ✅
NATURAL_LANGUAGEPass ✅
POWERSHELLPass ✅
PRE_COMMITPass ✅
SPELL_CODESPELLPass ✅
TRIVYPass ✅
YAMLPass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@MariusStorhaug