design/45713-workspace.md: mention that tools can help automate go.work creation
Change-Id: Ia02f7b637c5da39d111ce901696339ad5ad2fa12
Reviewed-on: https://go-review.googlesource.com/c/proposal/+/314729
Trust: Michael Matloob <matloob@golang.org>
Run-TryBot: Michael Matloob <matloob@golang.org>
Reviewed-by: Michael Matloob <matloob@golang.org>
diff --git a/design/45713-workspace.md b/design/45713-workspace.md
index f64819c..397ef2f 100644
--- a/design/45713-workspace.md
+++ b/design/45713-workspace.md
@@ -380,7 +380,9 @@
Our goal is that when there are several tightly coupled modules in the same
repository, users would choose to create `go.work` files defining the workspace
using the modules in those repositories instead of adding `replaces` in the
-`go.mod` files. These `go.work` files should not be checked into the
+`go.mod` files. Perhaps the creation of the file can be automated by an external
+tool that scans for all the `go.mod` files recursively contained in a directory.
+These `go.work` files should not be checked into the
repositories so that they don't override the workspaces users explicitly define.
Checking in `go.work` files could also lead to CI/CD systems not testing the
actual set of version requirements on a module and that version requirements
