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

term : remove "Dvcfile" from versioning use case tutorial #1526

Merged
merged 9 commits into from
Jul 6, 2020

Conversation

sarthakforwet
Copy link
Contributor

The following PR completes the below subtask from #1445.

versioning use case tutorial

Copy link
Contributor

@jorgeorpinel jorgeorpinel left a 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:

Comment on lines 326 to 328
`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
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
`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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

run

Do we need to change it from here also?

Copy link
Contributor

@jorgeorpinel jorgeorpinel Jul 6, 2020

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.

Copy link
Contributor

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.

Copy link
Contributor

Choose a reason for hiding this comment

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

@jorgeorpinel jorgeorpinel merged commit 6f066b8 into iterative:master Jul 6, 2020
@jorgeorpinel
Copy link
Contributor

Merged the restyled PR instead. Thanks @sarthakforwet

jorgeorpinel added a commit that referenced this pull request Jul 6, 2020
shcheklein pushed a commit that referenced this pull request Jul 6, 2020
shcheklein pushed a commit that referenced this pull request Jul 7, 2020
* cmd: rephrase intro of run
per #1526 (comment)

* cmd: typo in run -h out
per #1537 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants