pwsh-script
pwsh-script copied to clipboard
GitHub Action to run PowerShell scripts in a rich, prepared scope - inspired by actions/github-script.
Bumps [peter-evans/slash-command-dispatch](https://github.com/peter-evans/slash-command-dispatch) from 3 to 4. Release notes Sourced from peter-evans/slash-command-dispatch's releases. Slash Command Dispatch v4.0.0 ⚙️ Updated runtime to Node.js 20 The action now requires a minimum version of...
Demo
There's a [slash-command](https://github.com/peter-evans/slash-command-dispatch) available to try out the action. Simply comment on this issue with `/demo` in the first line and a PowerShell script in the following lines. If your...
Hi! When I run action and when the Run Amadevus/pwsh-script@v2 executes - there is an Error >Error: Invoke-Expression : Cannot bind argument to parameter 'Path' because it is null. >At...
Hi, I need to run some PowerShell commands as an admin. Is this possible? We're running on our own Github Actions Runners. Kind regards, Martin
Please consider publishing the `GitHubActionsCore` module in the PowerShell Gallery, so it's available outside of this action. That way, one may utilize `Get-ActionInput` and `Set-ActionOutput` too.
Within `GitHubActionsCore` PowerShell module we're currently missing some commands and options added since last release: - `notice` command - `getState` and `saveState` commands - `summary` commands (job/step summary) Source: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#about-workflow-commands
One thing I found myself always prepending to all my GitHub action PowerShell script is setting `$ProgressPreference` and `$InformationPreference`. - `$ProgressPreference` to `'Silent'`, because on the GitHub action log PowerShell...