From ae0e6e548e6449cda3c95ba614868e2a21eaf6db Mon Sep 17 00:00:00 2001 From: Kristof Mattei <864376+Kristof-Mattei@users.noreply.github.com> Date: Wed, 20 Oct 2021 20:35:03 -0700 Subject: [PATCH 1/2] Made `jobs..steps[*].shell` a separate ## --- .../workflow-syntax-for-github-actions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md index cf1876b155ea..aab547dab914 100644 --- a/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md +++ b/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md @@ -850,7 +850,7 @@ jobs: Runs command-line programs using the operating system's shell. If you do not provide a `name`, the step name will default to the text specified in the `run` command. -Commands run using non-login shells by default. You can choose a different shell and customize the shell used to run commands. For more information, see "[Using a specific shell](#using-a-specific-shell)." +Commands run using non-login shells by default. You can choose a different shell and customize the shell used to run commands. For more information, see "`jobs..steps[*].shell`](#jobsjob_idstepsrun)." Each `run` keyword represents a new process and shell in the runner environment. When you provide multi-line commands, each line runs in the same shell. For example: @@ -878,7 +878,7 @@ Using the `working-directory` keyword, you can specify the working directory of working-directory: ./temp ``` -### Using a specific shell +## `jobs..steps[*].shell` You can override the default shell settings in the runner's operating system using the `shell` keyword. You can use built-in `shell` keywords, or you can define a custom set of shell options. The shell command that is run internally executes a temporary file that contains the commands specified in the `run` keyword. From 4a177b0cf4249ed969ff9a99025589a08dbd0c33 Mon Sep 17 00:00:00 2001 From: Kristof Mattei <864376+Kristof-Mattei@users.noreply.github.com> Date: Wed, 20 Oct 2021 22:28:42 -0700 Subject: [PATCH 2/2] Corrected link rendering --- .../learn-github-actions/workflow-syntax-for-github-actions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md index aab547dab914..29b7215c776a 100644 --- a/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md +++ b/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md @@ -850,7 +850,7 @@ jobs: Runs command-line programs using the operating system's shell. If you do not provide a `name`, the step name will default to the text specified in the `run` command. -Commands run using non-login shells by default. You can choose a different shell and customize the shell used to run commands. For more information, see "`jobs..steps[*].shell`](#jobsjob_idstepsrun)." +Commands run using non-login shells by default. You can choose a different shell and customize the shell used to run commands. For more information, see [`jobs..steps[*].shell`](#jobsjob_idstepsshell). Each `run` keyword represents a new process and shell in the runner environment. When you provide multi-line commands, each line runs in the same shell. For example: