1
0
mirror of https://github.com/golang/go synced 2024-11-18 09:04:49 -07:00
go/gopls
Fazlul Shahriar 8a18b87bf6 all: fix broken links to LSP specification
Change-Id: Ied2cfa57012a8ec3c8bdd03a97fa7fc8bc744be9
Reviewed-on: https://go-review.googlesource.com/c/tools/+/198381
Reviewed-by: Rebecca Stambler <rstambler@golang.org>
Run-TryBot: Rebecca Stambler <rstambler@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
2019-10-02 18:32:53 +00:00
..
doc all: fix broken links to LSP specification 2019-10-02 18:32:53 +00:00
internal/hooks gopls: adding static check to the new gopls module 2019-09-23 16:54:24 +00:00
test gopls: refactor the cmd tests 2019-09-23 22:12:42 +00:00
go.mod gopls: adding static check to the new gopls module 2019-09-23 16:54:24 +00:00
go.sum gopls: adding static check to the new gopls module 2019-09-23 16:54:24 +00:00
main.go gopls: add a hooks package 2019-09-20 02:37:04 +00:00
README.md cmd/gopls: add documentation 2019-08-27 15:23:08 +00:00

gopls documentation

gopls (pronounced: "go please") is the official language server for the Go language.

It is currently in alpha, so it is not stable. You can see more information about the status of gopls and its supported features here.

In general you should not need to know anything about gopls, it should be integrated into your editor for you.

See the installing section of the user guide if you need to install or update gopls by hand.

Issues

If you are having issues with gopls, please first check the known issues before following the troubleshooting guide. If that does not give you the information you need, reach out to us.

You can chat with us on:

If you think you have an issue that needs fixing, or a feature suggestion, then please make sure you follow the steps to file an issue with the right information to allow us to address it.

If you need to talk to us directly (for instance to file an issue with confidential information in it) you can reach out directly to @stamblerre or @ianthehat.

More information

If you want to know more about it, have an unusual use case, or want to contribute, please read the following documents