-
Notifications
You must be signed in to change notification settings - Fork 18k
github: issue template should prompt if toolchain is go1.23 and above use go env -changed report bug #67767
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
Comments
Fixes golang#67767 Change-Id: I0bf267bc18d2a4f4ac27fb98319d6ea8b9d0ba07
Fixes golang#67767 Change-Id: I0bf267bc18d2a4f4ac27fb98319d6ea8b9d0ba07
Change https://go.dev/cl/589695 mentions this issue: |
|
issue template need |
I don't think we should do this. the full set of env vars is quite useful in picking out details which the reporter may not have otherwise thought to tell us about. |
I think we can decline this for the same reason as #67769 |
See #34208 , it background is that report an bug usually require the user to provide a
go env
, which has a problem the output is getting larger and larger, and most of it is usually useless.Now that
go env -changed
has been added, issue template should prompt the user to use it when the toolchain is greater than or equal to go1.23.The text was updated successfully, but these errors were encountered: