-
Notifications
You must be signed in to change notification settings - Fork 397
doc: regular updates (late Jan) #931
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
Conversation
install, checkout, commit, repro, and push per #931 (review)
fix formatting of user-guide/contributing
review "Nothing to reproduce." output samples (after `dvc repro`) rel: #938
41f234e
to
9e3d4fb
Compare
per iterative/dvc/pull/3277 and precursor to merging DVC repo term into DVC project (glossary)
6609de3
to
88c4546
Compare
data files. | ||
<!-- Separate MD quote: --> | ||
|
||
> See `dvc get` to download data/model files or directories from other <abbr>DVC |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
three notes in a raw - smells bad )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree. And import-url has 4 in a row... Will think about this ⏳
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
target to be downloaded within the source repository at `url`. It can point to | ||
any file or directory in there, including <abbr>outputs</abbr> tracked by DVC, | ||
as well as files tracked by Git. Note that for DVC repos, the target should be | ||
found in one of the [DVC-files](/doc/user-guide/dvc-file-format) pf the project. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pf - of?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed in #966
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
few typos, few unaddressed comments ... merging this anyway to prevent it from growing again, each review takes too much of my time since there are too many changes happen to all files at once
Other than "pf"? (Addressed)
Moving them to #966
Thank you! |
{ | ||
name: 'DVC Project', | ||
match: ['DVC project', 'project', 'projects'], | ||
match: [ | ||
'DVC project', | ||
'project', | ||
'projects', | ||
'DVC repository', | ||
'DVC repositories' | ||
], | ||
desc: ` | ||
Initialized by running \`dvc init\` in the **workspace** (typically in a Git | ||
repository). It will contain the | ||
[\`.dvc/\` directory](/doc/user-guide/dvc-files-and-directories) and | ||
[DVC-files](/doc/user-guide/dvc-file-format) created with commands such as | ||
\`dvc add\` or \`dvc run\`. It may also be a Git repository. | ||
` | ||
}, | ||
{ | ||
name: 'DVC Repository', | ||
match: ['DVC repository', 'DVC repositories'], | ||
desc: ` | ||
**DVC project** initialized using \`dvc init\` in a Git repository. It will | ||
contain \`.git/\` and [\`.dvc/\`](/doc/user-guide/dvc-files-and-directories) | ||
directories, as well as any DVC-files created by DVC. | ||
\`dvc add\` or \`dvc run\`. Some DVC commands require it to be in a Git repo – | ||
explained in each [command reference](/doc/command-reference) but usually | ||
obvious from the context. | ||
` | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These terms (DVC project and DVC repository) were merged per #931 (review), which was the right move. But after a short discussion in iterative/dvc#3277 (comment) I think maybe we should make "DVC repository" (or just repo) the main or only term?
Initially I only thought of repos as the Git part of DVC projects, but later on the term DVC repo started popping up and we even had its glossary entry, now we've merged them both but left "project" as the main term. Comparing vs the core DVC repo though, the term "project" is not used at all so it would be easier to just manage the single term "repo" even when sometimes it will be necessary to disambiguate between Git vs DVC – a problem we currently have anyway.
Thoughts @shcheklein ? I can do this in my next regular updates or in its own PR (if it affects lots of files) if so.
dvc pull
example in deep tut #946