From 28b43a5ac6862b14beea46e7778beca072df155f Mon Sep 17 00:00:00 2001 From: Rob Bos Date: Mon, 28 Aug 2023 16:04:08 +0200 Subject: [PATCH] Update README.md (#35) --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index b9f8aa6..28a40b3 100644 --- a/README.md +++ b/README.md @@ -71,3 +71,5 @@ If you want to hide certain warnings from shellcheck, then you can use the direc ``` shell # shellcheck disable=code ``` + +In some cases the directives are not picked up (might be depending on the shell it is checking. It can then help to add the `shell: your-shell-here` specification to your workflow file. I've seen this confusion happening with PowerShell code on a Windows based runner. Shellcheck was analyzing the script of the `run` step as if it where bash. The `shell` keyword was not needed for the workflow to run, as the default shell on the Windows runner was PowerShell already. Shellcheck cannot handle that. Specifying the keyword stopped the 'errors' from being reported.