From 1fbe47519419921992acc928b8a0707dfdda1824 Mon Sep 17 00:00:00 2001 From: James Pulec Date: Tue, 17 Sep 2024 21:34:14 -0700 Subject: [PATCH] Update constructing-ci.mdx (#9162) ### Description Fix minor typo. --- docs/repo-docs/crafting-your-repository/constructing-ci.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/repo-docs/crafting-your-repository/constructing-ci.mdx b/docs/repo-docs/crafting-your-repository/constructing-ci.mdx index 3c1d0321ba508..a55f348ede4e6 100644 --- a/docs/repo-docs/crafting-your-repository/constructing-ci.mdx +++ b/docs/repo-docs/crafting-your-repository/constructing-ci.mdx @@ -70,7 +70,7 @@ You'll want to use this flag in situations like: - You’re _not_ using a Remote Cache, but still want to do as little work as possible in CI. - You _are_ using a Remote Cache, and you’re in a large repository. By minimizing the amount of tasks that will be restored from cache, there will be less data to send across the network, resulting in faster cache restoration. - You’re already using [advanced filtering techniques](/repo/docs/reference/run#advanced-filtering-examples) or [`turbo-ignore`](/repo/docs/reference/turbo-ignore) to create the same or similar behavior as `--affected`. You likely have the opportunity to simplify your scripting using this new flag. - - `--affected` will can handle shallow clons more gracefully than bespoke filtering because it falls back to running all tasks. + - `--affected` will can handle shallow clones more gracefully than bespoke filtering because it falls back to running all tasks. ### Using `turbo-ignore`