Clarify behavior of dvc remove command in update-tracked-data guide
#5491
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
skshetry
approved these changes
Dec 3, 2025
Collaborator
skshetry
left a comment
skshetry
left a comment
There was a problem hiding this comment.
Thank you for contributing.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Clarifies the behavior of the
dvc removecommand in the "Update tracked data" guide.Why is this needed?
The previous documentation stated that
dvc remove train.tsv.dvcremovestrain.tsvfrom the workspace, which is incorrect. This command only removes the.dvcfile and unlinks the data from the cache, but the actual data file remains.Changes made
.dvcfile is removed and the data is unlinked from the cache, but the data file stays in the workspace.