commit | e78b40c7d0f9973e4a8ae8836f4b2131292d5609 | [log] [tgz] |
---|---|---|
author | Rebecca Stambler <rstambler@golang.org> | Tue Apr 06 17:59:09 2021 -0400 |
committer | Rebecca Stambler <rstambler@golang.org> | Wed Apr 07 17:38:53 2021 +0000 |
tree | 0a202f16dd6e75b9106e127bab8adaaaebe2a93f | |
parent | 3ac76b8bb7987237f88545d31e5be0c1acae3240 [diff] |
internal/lsp: switch to 'go get -u ./...' for transitive upgrades 'go get -u all' works for this in Go 1.16, but in earlier versions, we need 'go get -u ./...'. Also, include the -d and -t flags to avoid building binaries and to upgrade test dependencies. Fixes golang/go#45262 Change-Id: I8b04783ffcd53e8066c5a25fef72d91ae975f5a2 Reviewed-on: https://go-review.googlesource.com/c/tools/+/307889 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: Heschi Kreinick <heschi@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.