From bd0ecb6ac5554cfc2f18e44ceb136aa5b4b9f588 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Emil=20Bj=C3=B6rklund?= Date: Fri, 17 Oct 2025 13:31:53 +0200 Subject: [PATCH 1/2] docs: clarify passthrough args comparison ## Description The current docs for global hash inputs made me think that _any_ passthrough arg would invalidate the cache when present. Stupid, I know. But I read it several times and just could not parse the meaning correctly. The suggested fix would hopefully make it clear that the different examples are compared to the output of the first command. --- docs/site/content/docs/crafting-your-repository/caching.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/site/content/docs/crafting-your-repository/caching.mdx b/docs/site/content/docs/crafting-your-repository/caching.mdx index d9691e45c3d5f..7623d15c46b0b 100644 --- a/docs/site/content/docs/crafting-your-repository/caching.mdx +++ b/docs/site/content/docs/crafting-your-repository/caching.mdx @@ -169,7 +169,7 @@ Under the hood, Turborepo creates two hashes: a global hash and a task hash. If | [`globalDependencies`](/docs/reference/configuration#globaldependencies) file contents | Changing `./.env` when it is listed in `globalDependencies` will cause **all** tasks to miss cache | | Values of variables listed in [`globalEnv`](/docs/reference/configuration#globalenv) | Changing the value of `GITHUB_TOKEN` when it is listed in `globalEnv` | | Flag values that affect task runtime | Using behavior-changing flags like `--cache-dir`, `--framework-inference`, or `--env-mode` | -| Arbitrary passthrough arguments | `turbo build -- --arg=value` will miss cache compared to `turbo build` or `turbo build -- --arg=diff` | +| Arbitrary passthrough arguments | `turbo build -- --arg=value` will miss cache compared to either `turbo build` or `turbo build -- --arg=diff` | ### Package hash inputs From 49ae63e4caf3de20ef3787cc2a9af3487a978c09 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Emil=20Bj=C3=B6rklund?= Date: Fri, 17 Oct 2025 13:36:41 +0200 Subject: [PATCH 2/2] Missed a "when" --- docs/site/content/docs/crafting-your-repository/caching.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/site/content/docs/crafting-your-repository/caching.mdx b/docs/site/content/docs/crafting-your-repository/caching.mdx index 7623d15c46b0b..2eb015e6f632b 100644 --- a/docs/site/content/docs/crafting-your-repository/caching.mdx +++ b/docs/site/content/docs/crafting-your-repository/caching.mdx @@ -169,7 +169,7 @@ Under the hood, Turborepo creates two hashes: a global hash and a task hash. If | [`globalDependencies`](/docs/reference/configuration#globaldependencies) file contents | Changing `./.env` when it is listed in `globalDependencies` will cause **all** tasks to miss cache | | Values of variables listed in [`globalEnv`](/docs/reference/configuration#globalenv) | Changing the value of `GITHUB_TOKEN` when it is listed in `globalEnv` | | Flag values that affect task runtime | Using behavior-changing flags like `--cache-dir`, `--framework-inference`, or `--env-mode` | -| Arbitrary passthrough arguments | `turbo build -- --arg=value` will miss cache compared to either `turbo build` or `turbo build -- --arg=diff` | +| Arbitrary passthrough arguments | `turbo build -- --arg=value` will miss cache when compared to either `turbo build` or `turbo build -- --arg=diff` | ### Package hash inputs