cdadfa4ce7050cd6513e260d64f97eaa88c1f450 — Jason Miller 7 days ago 723ce99
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).
1 files changed, 1 insertions(+), 1 deletions(-)

M builds.sr.ht/index.md
M builds.sr.ht/index.md => builds.sr.ht/index.md +1 -1
@@ 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

Whenever you submit a build via the API, you can pass the `secrets` parameter (a