actions-marketplace-validations/BuildPipeScript

Builds code using PipeScript

Trust Signals

workflow.ymlSHA-pinned

uses: actions-marketplace-validations/startautomating_pipescript@be7b2e60bf10f60cc3422b0d6e72d71275392169 # no releases — HEAD as of 2026-07-10

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
Script	A PowerShell Script that uses PipeScript. Any files outputted from the script will be added to the repository. If those files have a .Message attached to them, they will be committed with that message.	no	—
SkipBuild	If set, will not run Build-PipeScript.	no	—
CommitMessage	If provided, will commit any remaining changes made to the workspace with this commit message. If no commit message is provided, if a GitHub Event contains a commit message, that message will be used. If no commit message is provided, and a commit message cannot be automatically detected, changes will not be committed.	no	—
InstallModule	A list of modules to be installed from the PowerShell gallery before scripts run. Note: If ugit is not installed, commit messages will not be carried properly with multiple commits.	no	ugit
Serial	If set, will build files one-by-one, instead of in parallel. This is currently the default.	no	—
Parallel	If set, will build files in parallel.	no	—
BatchSize	The number of files to build in each batch.	no	11
ThrottleLimit	The throttle limit for parallel jobs. If too many jobs are running at once, errors may occur.	no	7
UserEmail	The user email associated with a git commit.	no	—
UserName	The user name associated with a git commit.	no	—

no outputs