From feafd3e1d79a627b18e63705d1021165d978ba46 Mon Sep 17 00:00:00 2001 From: Justin Weissig Date: Mon, 26 Oct 2020 20:11:30 -0700 Subject: [PATCH] fixed grammar issues (#672) Nothing major here just minor wording. --- docs/adrs/0277-run-action-shell-options.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/adrs/0277-run-action-shell-options.md b/docs/adrs/0277-run-action-shell-options.md index 0383441d1..2b3c4110d 100644 --- a/docs/adrs/0277-run-action-shell-options.md +++ b/docs/adrs/0277-run-action-shell-options.md @@ -84,7 +84,7 @@ powershell/pwsh - Users can always opt out by not using the builtins, and providing a shell option like: `pwsh -File {0}`, or `powershell -Command "& '{0}'"`, depending on need cmd -- There doesnt seem to be a way to fully opt in to fail-fast behavior other than writing your script to check each error code and respond accordingly, so we cant actually provide that behavior by default, it will be completely up to the user to write this behavior into their script +- There doesn't seem to be a way to fully opt in to fail-fast behavior other than writing your script to check each error code and respond accordingly, so we can't actually provide that behavior by default, it will be completely up to the user to write this behavior into their script - cmd.exe will exit (return the error code to the runner) with the errorlevel of the last program it executed. This is internally consistent with the previous default behavior (sh, pwsh) and is the cmd.exe default, so we keep that behavior ## Consequences