From dc87fe556149e71cd9cc89a781eba43520f61b85 Mon Sep 17 00:00:00 2001 From: Jorge Orpinel Date: Sat, 15 Aug 2020 01:42:09 -0500 Subject: [PATCH] cmd: simplify explanation of what files are uploaded by push per https://github.com/iterative/dvc.org/pull/1602#pullrequestreview-465516419 --- content/docs/command-reference/push.md | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/content/docs/command-reference/push.md b/content/docs/command-reference/push.md index d5828cc302..fc5208ce61 100644 --- a/content/docs/command-reference/push.md +++ b/content/docs/command-reference/push.md @@ -47,14 +47,10 @@ directories), `.dvc` files, and stage names (found in `dvc.yaml`). 💡 For convenience, a Git hook is available to automate running `dvc push` after `git push`. See `dvc install` for more details. -Under the hood, a few actions are taken: - -- The push command checks the appropriate `dvc.lock` and `.dvc` files in the - workspace. -- For each output referenced in each stage or `.dvc` file, DVC - finds a corresponding file or directory in the cache. DVC then - gathers a list of files missing from the remote storage. -- The cached files missing from remote storage, if any, are uploaded. +For all outputs referenced in each target, DVC finds the +corresponding files and directories in the cache (identified by +hash values saved in `dvc.yaml` and `.dvc` files). DVC then gathers a list of +files missing from the remote storage, and uploads them. Note that the `dvc status -c` command can list files tracked by DVC that are new in the cache (compared to the default remote.) It can be used to see what files