diff options
author | Jason Miller <jasom@fastmail.com> | 2021-02-19 15:14:37 -0800 |
---|---|---|
committer | Drew DeVault <sir@cmpwn.com> | 2021-02-20 08:48:51 -0500 |
commit | cdadfa4ce7050cd6513e260d64f97eaa88c1f450 (patch) | |
tree | 9abddb808f593ddddfb9ebc8424d8944e44154d5 | |
parent | 723ce99786701f39f5ceaf0ef593afe3d803b54c (diff) | |
download | sr.ht-docs-cdadfa4ce7050cd6513e260d64f97eaa88c1f450.tar.gz |
Fix incorrect redirect example.
Redirects are processed left-to-right so '2>&1 >/dev/null' means:
'2>&1' redirects stderr to the original stdout
'>/dev/null' redirects just stdout to /dev/null, leaving stderr going to
the original stdout
Reversing the order causes stdout to redirect to /dev/null and then
stderr to go to the same place as stdout (which is /dev/null).
-rw-r--r-- | builds.sr.ht/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/builds.sr.ht/index.md b/builds.sr.ht/index.md index 8378c0a..7cbbf9a 100644 --- a/builds.sr.ht/index.md +++ b/builds.sr.ht/index.md @@ -95,7 +95,7 @@ make sure to run `set +x` first to temporarily disable detailed command logging in the build shell. Run `set -x` again once you're done handling secret information to re-enable command logging. You also need to be careful that secrets are not printed to stdout or stderr by the commands which use them -— add ` 2>&1 >/dev/null` to the affected commands if you need to hide this +— add ` >/dev/null 2>&1` to the affected commands if you need to hide this output. Whenever you submit a build via the API, you can pass the `secrets` parameter (a |