From c5782f5bc62fdda1dfefebb57f000d02940ad35a Mon Sep 17 00:00:00 2001 From: Ruslan Kuprieiev Date: Tue, 5 May 2020 20:20:37 +0300 Subject: [PATCH] docs: run: update --no-exec description (#1225) * docs: run: update --no-exec description Per https://github.com/iterative/dvc/pull/3729 * Update run.md --- content/docs/command-reference/run.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/docs/command-reference/run.md b/content/docs/command-reference/run.md index 0eef7fae8e..d60fd7e856 100644 --- a/content/docs/command-reference/run.md +++ b/content/docs/command-reference/run.md @@ -153,8 +153,10 @@ data pipeline (e.g. random numbers, time functions, hardware dependency, etc.) - `--no-exec` - create a stage file, but do not execute the `command` defined in it, nor track dependencies or outputs with DVC. In the DVC-file contents, the file hash values will be empty; They will be populated the next time this - stage is actually executed. This is useful if, for example, you need to build - a pipeline (dependency graph) first, and then run it all at once. + stage is actually executed. DVC will also add your outputs to `.gitignore`, + same as it would do without `--no-exec`. This is useful if, for example, you + need to build a pipeline (dependency graph) first, and then run it all at + once. - `--overwrite-dvcfile` - overwrite an existing DVC-file (with file name determined by the logic described in the `-f` option) without asking for