From 7550249b8019da9a31c2845b6cf66f3647f6c2eb Mon Sep 17 00:00:00 2001 From: Anthony Shew Date: Sun, 4 Aug 2024 15:29:48 -0600 Subject: [PATCH] docs: Re-mention passthroughs in CI compatibility section. --- .../crafting-your-repository/using-environment-variables.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/repo-docs/crafting-your-repository/using-environment-variables.mdx b/docs/repo-docs/crafting-your-repository/using-environment-variables.mdx index f0a4698761a42..267eb5ff7af55 100644 --- a/docs/repo-docs/crafting-your-repository/using-environment-variables.mdx +++ b/docs/repo-docs/crafting-your-repository/using-environment-variables.mdx @@ -109,9 +109,9 @@ For these cases, add those environment variables to [`globalPassThroughEnv`](/re #### CI vendor compatibility -Strict Mode will filter out environment variables that come from your CI vendors until you've accounted for them using `env` or `globalEnv`. +Strict Mode will filter out environment variables that come from your CI vendors until you've accounted for them using [`env`](/repo/docs/reference/configuration#env), [`globalEnv`](/repo/docs/reference/configuration#globalenv), [`passThroughEnv`](/repo/docs/reference/configuration#passthroughenv), or [`globalPassThroughEnv`](/repo/docs/reference/configuration#globalpassthroughenv). -If any of these variables are important to your build and aren't included by [Framework Inference](#framework-inference), make sure they are in your `turbo.json` configuration. +If any of these variables are important to your tasks and aren't included by [Framework Inference](#framework-inference), make sure they are in your `turbo.json` configuration. ### Loose Mode