You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -139,7 +139,7 @@ config:
139
139
# [DEPRECATED: use buildCommand instead] A list of flags passed to `go build`. Useful for passing `ldflags`.
140
140
buildFlags: []
141
141
# Command that's executed to lint the code
142
-
lintCommand: ["golangci-lint", "run]
142
+
lintCommand: ["golangci-lint", "run"]
143
143
```
144
144
145
145
### Yarn packages
@@ -213,7 +213,7 @@ This however can lead to subtle failure modes where a package built in one envir
213
213
214
214
To prevent such issues, leeway computes an _environment manifest_ which contains the versions of the tools used, as well as some platform information.
215
215
The entries in that manifest depend on the package types used by that workspace, e.g. if only `Go` packages exist in the workspace, only `go version`, [GOOS and GOARCH](https://golang.org/pkg/runtime/#pkg-constants) will be part of the manifest.
216
-
You can inspect a workspace's environment manifest using `leeway describe environment-manifest`.
216
+
You can inspect a workspace's environment manifest using `leeway describe environment-manifest`.
217
217
218
218
You can add your own entries to a workspace's environment manifest in the `WORKSPACE.yaml` like so:
cmd.Flags().Bool("werft", false, "Produce werft CI compatible output")
170
170
cmd.Flags().Bool("dont-test", false, "Disable all package-level tests (defaults to false)")
171
171
cmd.Flags().UintP("max-concurrent-tasks", "j", uint(runtime.NumCPU()), "Limit the number of max concurrent build tasks - set to 0 to disable the limit")
172
+
cmd.Flags().String("coverage-output-path", "", "Output path where test coverage file will be copied after running tests")
// we build the test binaries in addition to running the tests regularly, so that downstream packages can run the tests in different environments
911
928
{"sh", "-c", "mkdir _tests; for i in $("+goCommand+" list ./...); do "+goCommand+" test -c $i; [ -e $(basename $i).test ] && mv $(basename $i).test _tests; true; done"},
0 commit comments