-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
term: don't use "DVC-file" or "stage file" anymore, use ".dvc file" #3960
Comments
I would like to start working on the issue. @jorgeorpinel could you please clarify what's the difference between the term 'DVC-file' (according to #1366) used for dvc add/import/import-url and the term '.dvc file' used in all other cases? |
Hi @DiPaolo OK sure, thanks! TBH some or most of this may already be applied but it would be great to double check all the instances.
|
@jorgeorpinel thanks! It becomes much more clear now. One more question: I discovered the documentation on dvc.org widely operates with the term ".dvc file(s)", whereas you mentioned "DVC file" in your recent reply. What should I use while replacing outdated "DVC-file" and "stage file"? |
Wait I was confused @DiPaolo. I see this is a core repo issue. I was thinking about docs, where iterative/dvc.org/issues/1366 is already done. So yes, these terms are probably still pervasive in this repo. Reviewing and updating them would be ideal but keep in mind only the user-facing messages (e.g.
.dvc files are one kind of DVC files. See https://dvc.org/doc/user-guide/dvc-files, and the discussion in iterative/dvc.org/issues/1663 (feel free to participate there).
Depends on the context. If it specifically refers to .dvc files (e.g. in But if you find the terminology confusing I'm not sure you should jump into this issue yet. |
To match iterative/dvc.org/issues/1366 — which does not include updating any
dvc
command example output.Let's update all user output strings please, and hopefully debug output too. And then open a docs PR to reflect any of these changes, as usual.
The text was updated successfully, but these errors were encountered: