🩹 [Patch]: Local framework artifacts stay out of commits

[Marius Storhaug (MariusStorhaug)]

Template repositories now reserve the root /.PSModule/ directory for generated Process-PSModule artifacts. The directory and every nested artifact stay out of commits.

Fixed: generated framework artifacts stay out of commits

Local framework runs place build output, generated documentation, site content, and Pester reports beneath .PSModule/. Pester's temporary configuration and container state lives in the runner temporary directory rather than the consumer worktree. The template ignores the single repository artifact root without broadly ignoring files that may belong in source control.

Adopting this release

New repositories created from this template need no configuration, code, or invocation changes. The template's existing PSModule/Process-PSModule/.github/workflows/workflow.yml@v8 reference now includes the compatible framework migration. Existing repositories can add /.PSModule/ to their .gitignore when they adopt the current Process-PSModule v8 release.

Release impact

Field	Decision
Effective decision	release:patch, consistent with the patch classification in this PR title.
Semantic effect	Patch release: generated local artifacts no longer appear as untracked files.
Release/base coordinates	Final coordinates are resolved by the release process.

---

Technical details

Consumer change record

Identifier / surface	Before	After	Applicability / prerequisites	Consumer action	Verification
/.gitignore generated-artifact root	Framework output can be created in root outputs/, _site/, TestResult/, or CodeCoverage/ paths, with selected root paths ignored individually.	/.PSModule/ ignores the complete generated-artifact tree; Pester temporary state is outside the consumer worktree.	Repositories created from this template using Process-PSModule v8.	No configuration change for new template repositories. Existing repositories add the same ignore rule when adopting the framework version.	git check-ignore confirms nested .PSModule paths are ignored.

Template baseline

Field	Evidence
Producer identity	Released PSModule/Process-PSModule v8 reference at f04a481b1c7669f3e480f22b61e6d7fbbdd9311d, delivered by PSModule/Process-PSModule#540, uses released PSModule/Invoke-Pester v5.1.1 commit c5494aba3c07d7bfd81bdbbc9f301e8fa4a729fb, delivered by PSModule/Invoke-Pester#78.
Template identity	Candidate PSModule/Template-PSModule commit 9650691.
Compatibility evidence	Process workflow assertions require Pester report files beneath .PSModule/TestResult and .PSModule/CodeCoverage and reject root TestResult, CodeCoverage, and .temp paths; this template commit ignores the resulting artifact root.
Template work	This PR supplies the compatible template rule for the released framework behavior.

Maintainer evidence

Changed surface	Standards checked	Framework docs checked	Result
.gitignore	Code Layout	Process-PSModule generated-artifact paths	Aligned

Relevant issues (or links)

Related work

• Implemented by 🩹 [Patch]: Framework artifacts stay under .PSModule Process-PSModule#540
• Implemented by 🪲 [Fix]: Configured Pester report paths now work Invoke-Pester#78

[github-actions]

No Significant Changes Detected

This PR does not contain changes to files that would trigger a new release:

Pattern	Description
^src/	Matches files where path matches this pattern
^README\.md$	Matches files where path matches this pattern

Build, test, and publish stages will be skipped for this PR.

If you believe this is incorrect, please verify that your changes are in the correct locations.

[github-actions]

Super-linter summary

Language	Validation result
CHECKOV	Pass ✅
GITHUB_ACTIONS	Pass ✅
GITLEAKS	Pass ✅
GIT_MERGE_CONFLICT_MARKERS	Pass ✅
MARKDOWN	Pass ✅
NATURAL_LANGUAGE	Pass ✅
POWERSHELL	Pass ✅
PRE_COMMIT	Pass ✅
SPELL_CODESPELL	Pass ✅
TRIVY	Pass ✅
YAML	Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

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

[psmodule-s-shelly]

No Significant Changes Detected

This PR does not contain changes to files that would trigger a new release:

Pattern	Description
^src/	Matches files where path matches this pattern
^README\.md$	Matches files where path matches this pattern

Build, test, and publish stages will be skipped for this PR.

If you believe this is incorrect, please verify that your changes are in the correct locations.

[psmodule-s-shelly]

No Significant Changes Detected

This PR does not contain changes to files that would trigger a new release:

Pattern	Description
^src/	Matches files where path matches this pattern
^README\.md$	Matches files where path matches this pattern

Build, test, and publish stages will be skipped for this PR.

If you believe this is incorrect, please verify that your changes are in the correct locations.

[psmodule-s-shelly]

No Significant Changes Detected

This PR does not contain changes to files that would trigger a new release:

Pattern	Description
^src/	Matches files where path matches this pattern
^README\.md$	Matches files where path matches this pattern

Build, test, and publish stages will be skipped for this PR.

If you believe this is incorrect, please verify that your changes are in the correct locations.

[psmodule-s-shelly]

No Significant Changes Detected

This PR does not contain changes to files that would trigger a new release:

Pattern	Description
^src/	Matches files where path matches this pattern
^README\.md$	Matches files where path matches this pattern

Build, test, and publish stages will be skipped for this PR.

If you believe this is incorrect, please verify that your changes are in the correct locations.

[Copilot]

Copilot wasn't able to review any files in this pull request.