From 2b0abb3752f0c6821ff08e53178db646c34decc7 Mon Sep 17 00:00:00 2001 From: Eugene Plotnikov Date: Fri, 16 Feb 2024 12:48:49 +0400 Subject: [PATCH] a small addition to the `changed` flag (#5170) Co-authored-by: Vladimir --- docs/guide/cli.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guide/cli.md b/docs/guide/cli.md index 71d7b618c..64f85d0a6 100644 --- a/docs/guide/cli.md +++ b/docs/guide/cli.md @@ -135,9 +135,9 @@ vitest --api=false Run tests only against changed files. If no value is provided, it will run tests against uncommitted changes (including staged and unstaged). - To run tests against changes made in the last commit, you can use `--changed HEAD~1`. You can also pass commit hash or branch name. + To run tests against changes made in the last commit, you can use `--changed HEAD~1`. You can also pass commit hash (e.g. `--changed 09a9920`) or branch name (e.g. `--changed origin/develop`). - If paired with the `forceRerunTriggers` config option it will run the whole test suite if a match is found. + If paired with the [`forceRerunTriggers`](/config/#forcereruntriggers) config option it will run the whole test suite if at least one of the files listed in the `forceRerunTriggers` list changes. By default, changes to the Vitest config file and `package.json` will always rerun the whole suite. ### shard -- 2.51.2