Skip to content

Move framework actions into per-action folders (as-is)#1

Merged
Marius Storhaug (MariusStorhaug) merged 2 commits into
mainfrom
move-actions-into-folders
Jul 12, 2026
Merged

Move framework actions into per-action folders (as-is)#1
Marius Storhaug (MariusStorhaug) merged 2 commits into
mainfrom
move-actions-into-folders

Conversation

@MariusStorhaug

Copy link
Copy Markdown
Member

Summary

First step of the PSMA consolidation (PSModule/Process-PSModule#384): fold the framework-internal GitHub Actions into one repo, one folder per action, moved as-is.

Each action keeps its own action.yml + src/scripts + tests, so every action stays independently usable as PSModule/PSMA/<Action>@<ref> while we migrate. No logic changed in this PR — it only relocates the actions.

Folders added

  • Build-PSModule/
  • Test-PSModule/
  • Publish-PSModule/
  • Get-PSModuleSettings/
  • Resolve-PSModuleVersion/ (uses scripts/)
  • Install-PSModuleHelpers/
  • Document-PSModule/
  • Get-PesterCodeCoverage/
  • Get-PesterTestResults/

Copied per action: action.yml, the script dir (src/scripts), tests/, README.md. Skipped each source repo's .github/ (its own CI), LICENSE (repo root already has one), and dotfiles. The Template-Action root scaffolding is left untouched for now.

Next steps (separate PRs)

  1. Move any inline action.yml logic into the PowerShell scripts (most actions already just call a main script).
  2. Consolidate shared functions into a common PSMA module imported by a new root main.ps1 that dispatches on an activity input (e.g. main.ps1 Build, main.ps1 TestLocal), then re-point the Process-PSModule sub-workflows at PSMA.

Tracking: PSModule/Process-PSModule#384

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.

1 participant