From 0cd723208cb12b95589625250d13cf9ba0fc0cce Mon Sep 17 00:00:00 2001 From: Semir Patel Date: Mon, 29 Mar 2021 08:41:41 -0500 Subject: [PATCH] Fix spacing typo (#1872) --- docs/content/contributing/coding-style.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/contributing/coding-style.md b/docs/content/contributing/coding-style.md index 9b5a4be5..c8daf96b 100644 --- a/docs/content/contributing/coding-style.md +++ b/docs/content/contributing/coding-style.md @@ -9,7 +9,7 @@ When refactoring, writing or altering scripts, that is Shell and bash scripts, i 1. **Adjust your style of coding to the style that is already present**! Even if you do not like it, this is due to consistency. There was a lot of work involved in making all scripts consistent. 2. **Use `shellcheck` to check your scripts**! Your contributions are checked by GitHub Actions too, so you will need to do this. You can **lint your work with `make lint`** to check against all targets. 3. **Use the provided `.editorconfig`** file. -4. Use `/bin/bash` or `/usr/bin/envbash` instead of `/bin/sh`. Adjust the style accordingly. +4. Use `/bin/bash` instead of `/bin/sh`. Adjust the style accordingly. 5. `setup.sh` provides a good starting point to look for. 6. When appropriate, use the `set` builtin. We recommend `set -euEo pipefail` or `set -uE`.