cmd ref: dvc add 1.0 update#1411
Conversation
improve info on comments for DVC files&dirs guide per #1411 (comment)
| usage: dvc add [-h] [-q | -v] [-R] [--no-commit] [-f <filename>] | ||
| targets [targets ...] | ||
| usage: dvc add [-h] [-q | -v] [-R] [--no-commit] [--external] | ||
| [-f <filename>] targets [targets ...] |
There was a problem hiding this comment.
this has changed in 1.0 - it's --file now
There was a problem hiding this comment.
Good catch, will update...
There was a problem hiding this comment.
Extracted to #1426, please assign a priority - very recent change.
shcheklein
left a comment
There was a problem hiding this comment.
It's fine with me, but I'm a bit lost with these changes, at least with the name of a PR - quite a few changes here, but almost all of them are not related to 1.0 (and we actually didn't include some 1.0 related changes we made to dvc add at the same time)
Again, let's move forward (don't forget to update -f everywhere)
All the examples were reviewed with 1.0 and I also reviewed the whole description to see it's still current. Other than -f did you notice any other 1.0 change I missed? Thanks |
don't remember from the top of my head, the easiest way is to run |
|
-f wasn't included because it wasn't there when I did this changes, that PR was merged 2 days ago no docs issue/PR was started by core team: treeverse/dvc/pull/4004 I did notice this and left a message in the PR |
|
I ran -h at the time of making this PR of course. There's lots of ongoing core changes and it's not clear to me where the 1.0 release ends and the regular updates begin TBH it's causing some confusion e.g. treeverse/dvc#4011 (comment) |
I know. I mean that we can run |
|
Got it. Good idea, added a checkbox to the epic and created treeverse/dvc/issues/4024. For now this specific matter (add -f -> --file) is extracted to #1426 |
masteronce Regular updates & plots 1.0 update #1382 is merged.❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention
Fix #issue(if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.Please choose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏