It is the work of hundreds of contributors. We appreciate your help!
+## Before filing an issue
+
+If you are unsure whether you have found a bug, please consider asking in the [golang-nuts mailing
+list](https://groups.google.com/forum/#!forum/golang-nuts) or [other forums](https://golang.org/help/) first. If
+the behavior you are seeing is confirmed as a bug or issue, it can easily be re-raised in the issue tracker.
## Filing issues
-When filing an issue, make sure to answer these five questions:
+Sensitive security-related issues should be reported to [security@golang.org](mailto:security@golang.org).
+See the [security policy](https://golang.org/security) for details.
+
+The recommended way to file an issue is by running `go bug`.
+Otherwise, when filing an issue, make sure to answer these five questions:
1. What version of Go are you using (`go version`)?
2. What operating system and processor architecture are you using?
4. What did you expect to see?
5. What did you see instead?
-General questions should go to the [golang-nuts mailing list](https://groups.google.com/group/golang-nuts) instead of the issue tracker.
-The gophers there will answer or ask you to file an issue if you've tripped over a bug.
-
-Sensitive security-related issues should be reported to [security@golang.org](mailto:security@golang.org).
+For change proposals, see [Proposing Changes To Go](https://go.dev/s/proposal-process).
## Contributing code
-Please read the [Contribution Guidelines](https://golang.org/doc/contribute.html)
-before sending patches.
-
-**We do not accept GitHub pull requests**
-(we use [Gerrit](https://code.google.com/p/gerrit/) instead for code review).
+Please read the [Contribution Guidelines](https://golang.org/doc/contribute.html) before sending patches.
Unless otherwise noted, the Go source files are distributed under
the BSD-style license found in the LICENSE file.