Orchestrate module vs docs pipeline triggers

[Marius Storhaug (MariusStorhaug)]

Summary

• rename the top-level decision stage from Plan to Orchestrator in reusable workflows
• split change detection into explicit code and docs pattern groups
• allow docs/site publish path when docs/layout/config changes are present, even when module tests are skipped

Why

Issue review shows a common request to make pipeline routing event/change-aware rather than relying on one global pattern list. In particular:

• closesPublish docs when layout/config files change in PRs #405 (docs publish for layout/config-only changes)
• aligns with 🩹 [Patch]: Only create releases when significant changes are detected (module and documentation) #184 (separate module vs docs significance)
• aligns with Extract publish preconditions into a dedicated gate job #325, Support running the workflow on push to main, with prerelease-only-during-open-PR model #390, and Decouple PowerShell Gallery publish from GitHub Release creation #406 direction of explicit orchestration boundaries

Important change model

ImportantFilePatterns now supports grouped patterns in .github/PSModule.yml:

ImportantFilePatterns:
Code:
- '^src/(?!.*\.md$).*'Docs:
- '^README\.md$'
- '^src/.*\.md$'
- '^\.github/zensical\.toml$'
- '^zensical\.toml$'
- '^docs/'

Routing behavior:

• Code match => module build/test/release path runs
• Docs match => docs/site build+publish path runs
• Code match also counts as docs-impacting (generated docs depend on source)

Compatibility

• Legacy array format for ImportantFilePatterns still works and is treated as the Code list
• HasImportantChanges remains as a backward-compatible alias for HasModuleChanges
• New outputs: HasModuleChanges, HasDocsChanges

Scope

No change to module release label semantics; this PR upgrades orchestration/routing decisions.

[github-actions]

Super-linter summary

Language	Validation result
CHECKOV	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