-
Notifications
You must be signed in to change notification settings - Fork 394
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: stop using "DVC-file" and "stage file" #1366
Comments
Agreed. I haven't seen the |
@utkarshsingh99 I think this chore is a little too boring TBH, I don't want you to suffer with this any more! Can you just please remind us the list of files that have been done so far up to your 2nd PR (#1408)? Thanks again for the help, BTW! I'll take it from there.
|
Sure.
|
After 1.0, the term DVC-file only refers to raw/initial data versioned with
dvc add/import/import-url
. however users seem to mostly refer to such files as "dvc file" or.dvc
file or just[data].dvc
. Since we have all these alternatives, let's remove the formal term DVC-file? Also since there's notdvc.yaml
(pipelines file) which adds to the confusion.We could also address the "import stage" check box from #608:
I suggest we always use the specific[data].dvc
form in our docs.See these changes as an example of what to do: 1008321
UPDATE: Decided for
.dvc
file instead. See #1366 (comment) just below.UPDATE: Similarly, we should stop using "stage file" in favor for
.dvc
file as well.UPDATE: Do not include instances in DVC command output examples.
UPDATE: See #1366 (comment) for known progress
The text was updated successfully, but these errors were encountered: