New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/go: -cover flag documentation out of date #60438
Comments
-covermod
flag help message and wrong -cover
help message
-covermod
flag help message and wrong -cover
help message
Thanks @seankhliao for the title, I hit return too early. |
feel free to submit a PR/CL |
CC @thanm |
I'm not sure if this could be the chance to drop the |
Change https://go.dev/cl/498415 mentions this issue: |
Cover flag documentation was not up to date, and the -covermode flag documentation was missing. Fixes golang#60438 Change-Id: I11e769fa2a32d074de7a748aa534afdfe2ca4e78 Reviewed-on: https://go-review.googlesource.com/c/go/+/498415 TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Than McIntosh <thanm@google.com> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
While playing with the new
-cover
flag I was trying to see how to switch to thecovermod=count
.Running the
go help build
I've seen no available flag for it, but still the-covermod
flag is available and working fine.I've seen also that the
-cover
flag is showing a probably old message (theGOEXPERIMENT
env var is not required).I'm willing to help about this if is confirmed as an issue, or just a doc misalignment.
The docs says that it's generated with a
mkalldocs.sh
script, but I haven't found it.What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Run a
go help build
.What did you expect to see?
The "right"
-cover
flag message, and the missing-covermod
flag message.The text was updated successfully, but these errors were encountered: