-
Notifications
You must be signed in to change notification settings - Fork 394
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
term : remove "Dvcfile" from versioning use case tutorial #1526
Conversation
content/docs/use-cases/versioning-data-and-model-files/tutorial.md
Outdated
Show resolved
Hide resolved
content/docs/use-cases/versioning-data-and-model-files/tutorial.md
Outdated
Show resolved
Hide resolved
content/docs/use-cases/versioning-data-and-model-files/tutorial.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good in general. A few details:
`dvc run` creates a pipeline stage named `train` (specified using the `-n` | ||
option) in [`dvc.yaml`](/doc/user-guide/dvc-files-and-directories#dvcyaml-file) | ||
file. It tracks all outputs (`-o`) the same way as `dvc add` does. Unlike |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`dvc run` creates a pipeline stage named `train` (specified using the `-n` | |
option) in [`dvc.yaml`](/doc/user-guide/dvc-files-and-directories#dvcyaml-file) | |
file. It tracks all outputs (`-o`) the same way as `dvc add` does. Unlike | |
`dvc run` writes a pipeline stage named `train` (specified using the `-n` | |
option) in [`dvc.yaml`](/doc/user-guide/dvc-files-and-directories#dvcyaml-file). | |
It tracks all outputs (`-o`) the same way as `dvc add` does. Unlike |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes but it's out of scope. The whole ref. needs to be rewritten soon. I'm committing my suggestion above to save time. Please just fix the formatting. Resolving here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually the command was already rewritten so yes, just this intro to that command should be rephrased... But still, out of scope for this PR. I'll send a separate one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
content/docs/use-cases/versioning-data-and-model-files/tutorial.md
Outdated
Show resolved
Hide resolved
content/docs/use-cases/versioning-data-and-model-files/tutorial.md
Outdated
Show resolved
Hide resolved
…l.md Co-authored-by: Jorge Orpinel <[email protected]>
Co-authored-by: Jorge Orpinel <[email protected]>
Merged the restyled PR instead. Thanks @sarthakforwet |
* cmd: rephrase intro of run per #1526 (comment) * cmd: typo in run -h out per #1537 (comment)
The following PR completes the below subtask from #1445.