fix: Fix flag ordering in set calls in scripts (#99)
The README for scripts has an incorrect use of the `set`. Where it says to use: set -oue pipefail it should be: set -euo pipefail since `pipefail` is an option consumed by `set -o`. More information: https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html
This commit is contained in:
parent
e530978bb4
commit
17bacbe3da
24 changed files with 25 additions and 25 deletions
|
|
@ -1,7 +1,7 @@
|
|||
#!/usr/bin/env bash
|
||||
|
||||
# Tell build process to exit if there are any errors.
|
||||
set -oue pipefail
|
||||
set -euo pipefail
|
||||
|
||||
get_yaml_array SCRIPTS '.scripts[]' "$1"
|
||||
|
||||
|
|
@ -13,4 +13,4 @@ find "$PWD" -type f -exec chmod +x {} \;
|
|||
for SCRIPT in "${SCRIPTS[@]}"; do
|
||||
echo "Running script $SCRIPT"
|
||||
eval "$PWD/$SCRIPT"
|
||||
done
|
||||
done
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue