From 47387eb9e6c7d864638142c8a5c8c0d1cfe608f0 Mon Sep 17 00:00:00 2001 From: Josh Johanning Date: Fri, 19 Aug 2022 15:18:37 -0500 Subject: [PATCH] adding note about sh and bash --- .../actions/jobs/section-running-jobs-in-a-container.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/data/reusables/actions/jobs/section-running-jobs-in-a-container.md b/data/reusables/actions/jobs/section-running-jobs-in-a-container.md index 7c9ff2e3fa..5bc5064955 100644 --- a/data/reusables/actions/jobs/section-running-jobs-in-a-container.md +++ b/data/reusables/actions/jobs/section-running-jobs-in-a-container.md @@ -2,6 +2,8 @@ Use `jobs..container` to create a container to run any steps in a job th If you do not set a `container`, all steps will run directly on the host specified by `runs-on` unless a step refers to an action configured to run in a container. +Note: the default shell for `run` steps inside a container is `sh` instead of `bash`. This can be overridden with [`jobs..defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaultsrun) or [`jobs..steps[*].shell`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsshell). + ### Example: Running a job within a container ```yaml{:copy}