From 961a24da62b6827136d424c0e5e33e14df617827 Mon Sep 17 00:00:00 2001 From: Jorge Orpinel Date: Fri, 28 Jan 2022 00:11:46 -0600 Subject: [PATCH] ref: link "stage" concept to `run` ref. for now rel. https://github.com/iterative/dvc.org/pull/3223#discussion_r793878165 --- content/docs/command-reference/freeze.md | 4 ++-- content/docs/command-reference/import-url.md | 13 ++++++++----- .../docs/user-guide/experiment-management/index.md | 2 +- 3 files changed, 11 insertions(+), 8 deletions(-) diff --git a/content/docs/command-reference/freeze.md b/content/docs/command-reference/freeze.md index 1994cfb90b..758300cac4 100644 --- a/content/docs/command-reference/freeze.md +++ b/content/docs/command-reference/freeze.md @@ -1,6 +1,6 @@ # freeze -Freeze [stages](/doc/command-reference/stage) until `dvc unfreeze` is used on +Freeze [stages](/doc/command-reference/run) until `dvc unfreeze` is used on them. Frozen stages are never executed by `dvc repro`. ## Synopsis @@ -14,7 +14,7 @@ positional arguments: ## Description -`dvc freeze` causes the [stages](/doc/command-reference/stage) indicated as +`dvc freeze` causes the [stages](/doc/command-reference/run) indicated as `targets` to be considered _not changed_ by `dvc status` and `dvc repro`. Stage reproduction will not regenerate outputs of frozen stages, even if their dependencies have changed, and even if `--force` is used. diff --git a/content/docs/command-reference/import-url.md b/content/docs/command-reference/import-url.md index 1493e85b55..f3c996be35 100644 --- a/content/docs/command-reference/import-url.md +++ b/content/docs/command-reference/import-url.md @@ -100,9 +100,12 @@ DVC supports several types of external locations (protocols): necessary to track if the specified URL changed. Another way to understand the `dvc import-url` command is as a shortcut for -generating a pipeline stage with and external dependency. This is discussed in -the [External Dependencies](/doc/user-guide/external-dependencies) -documentation, where an alternative is demonstrated for each of these schemes. +generating a pipeline [stage](/doc/command-reference/run) with and external +dependency. + +> This is discussed in the +> [External Dependencies](/doc/user-guide/external-dependencies) documentation, +> where an alternative is demonstrated for each of these schemes. Instead of: @@ -121,8 +124,8 @@ $ dvc stage add -n download_data \ $ dvc repro ``` -`dvc import-url` generates an _import `.dvc` file_ and `dvc stage add` a regular -stage (in `dvc.yaml`). +`dvc import-url` generates an _import `.dvc` file_ while `dvc stage add` +produces a regular stage in `dvc.yaml`. ## Options diff --git a/content/docs/user-guide/experiment-management/index.md b/content/docs/user-guide/experiment-management/index.md index b032c7e18e..bf4e15ce38 100644 --- a/content/docs/user-guide/experiment-management/index.md +++ b/content/docs/user-guide/experiment-management/index.md @@ -79,7 +79,7 @@ until your experiments are made [persistent]. Every time you [reproduce](/doc/command-reference/repro) a pipeline with DVC, it logs the unique signature of each stage run (in `.dvc/cache/runs` by default). -If it never happened before, the stage command(s) are executed normally. Every +If it never happened before, its command(s) are executed normally. Every subsequent time a [stage](/doc/command-reference/run) runs under the same conditions, the previous results can be restored instantly, without wasting time or computing resources.