jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-25 02:17:36 -05:00
Code Issues Projects Releases Wiki Activity

Change docs around -eo pipefail when shell is not specified

Browse Source
This commit is contained in:
Nikola Jokic
2022-07-05 10:26:21 +02:00
committed by GitHub
parent 7ada1b26cf
commit e34b844050
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/actions/using-workflows/workflow-syntax-for-github-actions.md
View File

@@ -630,8 +630,8 @@ For information about the software included on GitHub-hosted runners, see "[Spec
For built-in shell keywords, we provide the following defaults that are executed by {% data variables.product.prodname_dotcom %}-hosted runners. You should use these guidelines when running shell scripts.
- `bash`/`sh`:
- Fail-fast behavior using `set -eo pipefail`: Default for `bash` and built-in `shell`. It is also the default when you don't provide an option on non-Windows platforms.
- You can opt out of fail-fast and take full control by providing a template string to the shell options. For example, `bash {0}`.
- Fail-fast behavior using `set -eo pipefail`: This option is set when `shell: bash` is specified explicitly. It is not applied by default.
- You can take full control over shell parameters by providing a template string to the shell options. For example, `bash {0}`.
- sh-like shells exit with the exit code of the last command executed in a script, which is also the default behavior for actions. The runner will report the status of the step as fail/succeed based on this exit code.
- `powershell`/`pwsh`