-
Notifications
You must be signed in to change notification settings - Fork 386
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
how to: "undo" 'dvc add' + other "how to undo mistakes" recipes #625
Comments
@gwerbin There is an example of how to undo |
There is also a stackexchange about DS: https://datascience.stackexchange.com |
I feel that there should be an easier way) |
@Suor do you meant that there is an easier way already, or rather that it's a good sign to implement one? like |
@shcheklein I don't see one, but there probably should be. I am surprised |
BTW, this recipe is also dangerous considering how |
@Suor agreed! Could you create a ticket for this on the DVC core repo? I also think that using current |
Removing file from cache by hand is also unsafe, that one might be referenced somewhere else. |
This issue is 1 of 3 that I was asked to post here, following a conversation on Discord with mroutis and ivan
I encountered this problem within my first 15 minutes of using DVC: "how do I undo
dvc add
?"The answer turns out to be:
unprotect
the file, just in casegc
or look up the MD5 indata.dvc
and delete it from.dvc/cache
by hand.It would be nice if this recipe were included somewhere in the docs.
Part of the reason this procedure was so non-obvious is that I never thought to look in https://dvc.org/doc/commands-reference/add. This turns out to have a complete technical explanation of linking, and what "protect" means in DVC. This document should be referenced early and often, maybe with a sentence like "For a technical explanation of the caching and linking process, see here".
In the meantime, hopefully my Stackoverflow self-answer will help other users, as well as get the DVC ball rolling on Stackoverflow.
DVC, like Git, admits the possibility of potentially-destructive beginner mistakes. I think it would be good practice to try and anticipate and provide recipes for undoing mistakes, and link to them prominently in the getting started documentation.
The text was updated successfully, but these errors were encountered: