From f39f8dc5d4cdafc2045a47aeb90a1f921654872b Mon Sep 17 00:00:00 2001 From: Ed Page Date: Tue, 13 Sep 2022 14:08:01 -0500 Subject: [PATCH] docs(ref): Provide path for people to finding why shared Cargo.lock matters --- src/doc/src/reference/workspaces.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/doc/src/reference/workspaces.md b/src/doc/src/reference/workspaces.md index 867596bedf7..03e7b02ff23 100644 --- a/src/doc/src/reference/workspaces.md +++ b/src/doc/src/reference/workspaces.md @@ -6,7 +6,7 @@ members*, that are managed together. The key points of workspaces are: * Common commands can run across all workspace members, like `cargo check --workspace`. -* All packages share a common `Cargo.lock` file which resides in the +* All packages share a common [`Cargo.lock`] file which resides in the *workspace root*. * All packages share a common [output directory], which defaults to a directory named `target` in the *workspace root*. @@ -240,6 +240,7 @@ to the data in `workspace.metadata` if data is missing from `package.metadata`, if that makes sense for the tool in question. [package]: manifest.md#the-package-section +[`Cargo.lock`]: ../guide/cargo-toml-vs-cargo-lock.md [package-metadata]: manifest.md#the-metadata-table [output directory]: ../guide/build-cache.md [patch]: overriding-dependencies.md#the-patch-section