commit | a1b87a1c0de44760bd00894ef736a8c36548068f | [log] [tgz] |
---|---|---|
author | Rebecca Stambler <rstambler@golang.org> | Tue Nov 24 16:59:07 2020 -0500 |
committer | Rebecca Stambler <rstambler@golang.org> | Tue Dec 01 19:22:19 2020 +0000 |
tree | 04b84c36beac06390a294ab9c3d1f1e026901a50 | |
parent | 5fbf2908eb8fa700dbb49629de59925c1814e112 [diff] |
internal/lsp: track all go.mod changes no matter the workspace mode In some cases (such as presenting more helpful error messages), we need to know the number of go.mod files in the workspace--not just the active go.mod files. Track both known and active mod files separately. Change-Id: I068f76c2930c90cd0fdf5ce637e5934210880f65 Reviewed-on: https://go-review.googlesource.com/c/tools/+/273047 Trust: Rebecca Stambler <rstambler@golang.org> Run-TryBot: Rebecca Stambler <rstambler@golang.org> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Robert Findley <rfindley@google.com>
This subrepository holds the source for various packages and tools that support the Go programming language.
Some of the tools, godoc
and vet
for example, are included in binary Go distributions.
Others, including the Go guru
and the test coverage tool, can be fetched with go get
.
Packages include a type-checker for Go and an implementation of the Static Single Assignment form (SSA) representation for Go programs.
The easiest way to install is to run go get -u golang.org/x/tools/...
. You can also manually git clone the repository to $GOPATH/src/golang.org/x/tools
.
This repository uses prettier to format JS and CSS files.
The version of prettier
used is 1.18.2.
It is encouraged that all JS and CSS code be run through this before submitting a change. However, it is not a strict requirement enforced by CI.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.
The main issue tracker for the tools repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/tools/(your subdir):” in the subject line, so it is easy to find.