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.

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
Changes from 1 commit
Commits
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
5 changes: 3 additions & 2 deletions content/docs/command-reference/run.md
Original file line number Diff line number Diff line change
Expand Up @@ -153,8 +153,9 @@ 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 add your outputs to `.gitignore` to
prevent possible future conflicts. This is useful if, for example, you need to
build a pipeline (dependency graph) first, and then run it all at once.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clearly could be worded/explained better. Suggestions are welcome πŸ™‚

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure I understand this to prevent possible future conflicts to even suggest improvements :)


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

Expand Down