-
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
docs: update files/dirs for 1.0 release #1215
Conversation
Co-authored-by: Restyled.io <[email protected]>
- `.dvc/tmp`: Directory for miscellaneous temporary files | ||
|
||
- `.dvc/tmp/index`: Directory for remote index files that are used for | ||
optimizing `dvc push/pull/fetch/status -c` operations. |
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.
it creates a link automatically to the commands, better split this into more verbose but clean:
dvc pull -c
, dvc push -c
etc
Great! Should we create a tag in this repo before any 1.0 changes, so we can release a pdf version of the docs for 0.9? If so, was this the first 1.0-related change? Thanks |
- `.dvc/tmp/updater`: This file is used store the latest available version of | ||
DVC. It's used to remind the user to upgrade when the installed version is | ||
behind. |
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.
Why do we need to document for .dvc/tmp
directory at all?
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.
@skshetry Sure, we could make it a black box, but people will still get nosy and will ask questions. So easier to document it once and for all 🙂
Per iterative/dvc#3725
❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention
Fix #issue
(if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.Please chose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏