Corrections in #27 applied. Titles changed back to "Step n" #33
Conversation
| "title": "Track a file or directory", | ||
| "title": "Step 1", | ||
| "text": "01-track-a-file-or-directory.md" |
There was a problem hiding this comment.
Alternatively we could keep the full titles here and remove the # (H1) titles from .md files.
There was a problem hiding this comment.
I guess that how it was before this change. OK, as you prefer 👍
| > `data.xml`. Let's check whether the hash calculated by `md5sum` is identical | ||
| > with the hash calculated by DVC. |
There was a problem hiding this comment.
Let's check whether the hash calculated by
md5sumis identical with the hash calculated by DVC.
Oops, this part was OK as a regular paragraph.
| The command `dvc status` can compare the data on the workspace with the data saved | ||
| on the cache. | ||
|
|
||
| to compare files between the data stored on cache and the default remote. | ||
| `dvc status --cloud`{{execute}} | ||
|
|
||
| Without the `-c, --cloud` option | ||
|
|
||
| `dvc status`{{execute}} | ||
|
|
||
| checks whether workspace files are up to date with _local cache._ | ||
| checks whether workspace files are up to date with the _local cache._ |
There was a problem hiding this comment.
This order is still confusing IMO. Why not use plain status first and -c after?
There was a problem hiding this comment.
Or just mention plain status first (without executable command) and go on to using status -c which is what matters at this point. Plain status is used later.
|
Thank you @iesahin it feels more streamlined now for sure 🙏 |
This fixes #27. Thank you @jorgeorpinel