From a6acd2a2d58327de04fb27dc4c837cdb386e7c15 Mon Sep 17 00:00:00 2001 From: Alex Willmer Date: Wed, 15 Oct 2025 20:44:15 +0100 Subject: [PATCH] docs: Note the evalution order of environment variables (#2618) * docs: Note the evalution order of environment variables * Remove example that doesn't reinforce good practice Co-authored-by: Joe Rickerby --------- Co-authored-by: Joe Rickerby --- docs/options.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/options.md b/docs/options.md index 9f02fffe..1c4e89d8 100644 --- a/docs/options.md +++ b/docs/options.md @@ -572,6 +572,7 @@ A list of environment variables to set during the build and test phases. Bash sy You must use this variable to pass variables to Linux builds, since they execute in a container. It also works for the other platforms. You can use `$PATH` syntax to insert other variables, or the `$(pwd)` syntax to insert the output of other shell commands. +Variables are evaluated in the order they appear. Any variable referenced before it is set will evaluate to an empty string. To specify more than one environment variable, separate the assignments by spaces.