Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: run: update --no-exec description #1225

Merged
merged 2 commits into from
May 5, 2020
Merged

docs: run: update --no-exec description #1225

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
df6e3e5
docs: run: update --no-exec description
efiop May 3, 2020
0125ea8
Update run.md
efiop May 5, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions content/docs/command-reference/run.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

- `-y`, `--yes` (_deprecated_) - See `--overwrite-dvcfile` below.

Expand Down