From eb568b474d5247606e7b5b187746f2ea1d86f26b Mon Sep 17 00:00:00 2001 From: Jorge Orpinel Date: Mon, 21 Dec 2020 13:57:10 -0600 Subject: [PATCH] term: review "stage file" in recent blogs --- content/blog/2020-04-16-april-20-community-gems.md | 10 +++++----- content/blog/2020-06-22-dvc-1-0-release.md | 2 +- content/blog/2020-07-22-july-20-community-gems.md | 2 +- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/content/blog/2020-04-16-april-20-community-gems.md b/content/blog/2020-04-16-april-20-community-gems.md index 584c29d89e..a7817ff31d 100644 --- a/content/blog/2020-04-16-april-20-community-gems.md +++ b/content/blog/2020-04-16-april-20-community-gems.md @@ -129,12 +129,12 @@ modify its corresponding DVC file. It's handy so you don't rename a file in your local workspace that's under DVC tracking without updating DVC to the change (see an [example here](https://dvc.org/doc/command-reference/move#description)). The function doesn't work on -[stage files](https://dvc.org/doc/tutorials/pipelines#define-stages) from DVC -pipelines. There's not currently an easy way to safely move stage files, and -it's an +["stage files"](https://dvc.org/doc/tutorials/pipelines#define-stages) from DVC +pipelines. There's not currently an easy way to safely move `dvc.yaml` files, +and it's an [open issue we're working on](https://github.com/iterative/dvc/issues/1489). -Until then, you can manually update the stage file, or make a new one in the -desired location. +Until then, you can manually update `dvc.yaml`, or make a new one in the desired +location. ### Q: [I just starting using DVC and noticed that when I `dvc push` files to remote cloud storage, the directory in my remote looks like my DVC cache, not my local workspace directory. Is this right?](https://discordapp.com/channels/485586884165107732/485596304961962003/693740598498426930) diff --git a/content/blog/2020-06-22-dvc-1-0-release.md b/content/blog/2020-06-22-dvc-1-0-release.md index 456df34194..1632be455a 100644 --- a/content/blog/2020-06-22-dvc-1-0-release.md +++ b/content/blog/2020-06-22-dvc-1-0-release.md @@ -65,7 +65,7 @@ pipelines with data processing steps. People need to change the commands of the pipeline often and it was not easy to do this with the old DVC-files. In DVC 1.0, the DVC metafile format was changed in three big ways. First, -instead of multiple DVC stage files (`*.dvc`), each project has a single +instead of multiple DVC "stage files" (`*.dvc`), each project has a single `dvc.yaml` file. By default, all stages go in this single YAML file. Second, we made clear connections between the `dvc run` command (a helper to diff --git a/content/blog/2020-07-22-july-20-community-gems.md b/content/blog/2020-07-22-july-20-community-gems.md index 9a64f38fb4..da47517f38 100644 --- a/content/blog/2020-07-22-july-20-community-gems.md +++ b/content/blog/2020-07-22-july-20-community-gems.md @@ -53,7 +53,7 @@ If for some reason this won't work for your team, you can either downgrade to a previous version, or use a workaround: ```dvc -$ dvc repro <.dvc stage file> +$ dvc repro <.dvc file> ``` substituting the appropriate `.dvc` file for your pipeline. DVC 1.0 is backwards