cmd: copy edits for import-url ref.#1494
Conversation
|
You could add the "This" -> "These" update here 😉 |
|
Fix #1492 |
|
@jorgeorpinel I found |
|
|
||
| You may want to get out of and remove the `example-get-started/` directory after | ||
| trying this example (especially if trying out the following one). | ||
|
|
There was a problem hiding this comment.
I believe this statement is irrelevant here since anyone could arrive at this page without going through the User Guide/Getting-Started and it does not hold a direct info about the import-url command.
There was a problem hiding this comment.
I don't think you followed the entire examples section first. That would need to be done to determine this. Feel free to do so and submit a different PR if you find this unnecessary, but it's out of scope for this PR. Please roll back here. Thanks
There was a problem hiding this comment.
Alright.
But do you think it should be removed?
I don't think you followed the entire examples section first.
Actually, since this is in command reference, I thought it would be good to keep this file independent of the Getting Started module
There was a problem hiding this comment.
I don't think it should be removed. But like I mentioned, I would need to follow the entire examples section first to decide.
would be good to keep this file independent of the Getting Started
It is. Again, I don't think you read the whole examples section 🙂
Please roll back.
There was a problem hiding this comment.
Oh okay. Now I get it. It's just related to the example above.
My apologies 😄
This comment has been minimized.
This comment has been minimized.
Please say specifically which part of that issue is addressed in the description of this PR (you can just copy the entire import/import-url checkbox here, and mark it).
FYI special keywords only work on the PR description. Not needed here anyway because I already closed that issue as fixed.
I see that import only has |
| The `deps` field in the generated `.dvc` file contains a hash value along with | ||
| the `path` to track changes in the remote file/directory. The hash type depends | ||
| on the type of remote location (protocol) being tracked. For instance, | ||
| files/directories tracked from HTTP(s)/S3/Azure/GS remote locations will have an |
There was a problem hiding this comment.
I made a mistake with the comment. GS uses md5. Sorry about that.
There was a problem hiding this comment.
Okay, I'll change it in the DVC Files and Directories page in the next commit ✌️
There was a problem hiding this comment.
No worries @skshetry, glad you caught it though! Thanks for the followup. I updated #1469 and fixed the dvc.lock doc in another PR. But this brings some questions... I'll ping you somewhere else.
@utkarshsingh99 please update the paragraph above accordingly...
This comment has been minimized.
This comment has been minimized.
There's one mention of adding external files in |
|
Nah actually add is a special case. Those aren't deps, they're outs. Don't worry about that for now. But what about |
|
Removed this
Added:
Just adding this here since I got a bit confused with 2 reviews here: #1494(comment) and #1494(another comment). |
| The `deps` field in the generated `.dvc` file contains a hash value along with | ||
| the `path` to track changes in the remote file/directory. The hash type depends | ||
| on the type of remote location (protocol) being tracked. See | ||
| [`dvc.lock` file](/doc/user-guide/dvc-files-and-directories#dvclock-file) for | ||
| info on hash types for specific remote location types. | ||
|
|
There was a problem hiding this comment.
Yeah this whole paragraph is probably unnecessary but thanks. The ref. is already too long TBH. Users can find out about .dvc file specs in its dedicated guide, that's not the main purpose for a command ref.
There was a problem hiding this comment.
Okay, so where should I link dvc.lock file ?
There was a problem hiding this comment.
Why did you decide to edit this command reference if there's no existing places that relate to dvc.lock? I'm going to just merge this with the few typo fixed but I'll have to uncheck that box in the original index so this can be re-evaluated.
There was a problem hiding this comment.
I actually thought that we needed to add some reference to the hash values in each file or describe where it was needed based on the original issue. But does this mean that there is no place we can add a reference to dvc.lock or provide info about different types of file hashes in import-url?
There was a problem hiding this comment.
does this mean that there is no place we can add a reference to dvc.lock or provide info about different types of file hashes in import-url?
Idk, can you answer that question? 🙂 Let's go back to analyzing the checkboxes of #1469 and please comment there if any one seems unaplicable.
Ah yeah, it's the first one: remove whole paragraph. Thanks |
❗ 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. 🙏
Partially address #1469