diff options
| author | Michael Matloob <matloob@golang.org> | 2021-04-28 13:41:48 -0400 |
|---|---|---|
| committer | Michael Matloob <matloob@golang.org> | 2021-06-15 18:06:31 +0000 |
| commit | 7516fd617dcde3835d1a09148dbec1a3cac474a9 (patch) | |
| tree | d2853fd0e4eee42a342ae0f23ad6ff77ecf26115 | |
| parent | 3334b5244f594da72160fc72ef26cb5f359955ec (diff) | |
| download | go-x-proposal-7516fd617dcde3835d1a09148dbec1a3cac474a9.tar.xz | |
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>
| -rw-r--r-- | design/45713-workspace.md | 4 |
1 files changed, 3 insertions, 1 deletions
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 @@ requirements on released modules which is out of scope for this proposal. 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 |