| commit | abd3201226033fea9947479104d60c2c9ee954c7 | [log] [tgz] |
|---|---|---|
| author | thepudds1460 <thepudds1460@gmail.com> | Sat Dec 21 06:36:27 2024 -0500 |
| committer | Gopher Robot <gobot@golang.org> | Mon Dec 23 06:46:44 2024 -0800 |
| tree | ee3f8f8ff729ed8f89988854d2ebfd4e72e54139 | |
| parent | 73152bbfa6fb4f665c3d4736457071dd53c134e3 [diff] |
_content/doc/go1.24: fix meaning of -u in 'go get -u tool' It's a common misperception that -u is needed more often than it is, perhaps in part due to muscle memory from the GOPATH days. The current release notes suggest that 'go get -u tool' will upgrade all of the current module's tools, but it does more than that -- it will also upgrade all of the direct and indirect non-test dependencies of those tools too. The simplest fix is probably just to remove the -u from this section of the release notes. There are various other details that could be covered, like the -u or -t flags, or that 'go get tool' is a shorthand for 'go get tool@upgrade', but maybe this is sufficient. Updates golang/go#48429 Updates golang/go#68545 Change-Id: I31eeb96dae996a7ffde24d9bae6788d6889e2044 Reviewed-on: https://go-review.googlesource.com/c/website/+/638296 Reviewed-by: David Chase <drchase@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Conrad Irwin <conrad.irwin@gmail.com>
This repo holds content and serving programs for the go.dev and golang.org web sites.
Content is in _content/ (go.dev) and tour/ (go.dev/tour). Server code is in cmd/ and internal/.
To run the combined go.dev+golang.org server to preview local content changes, use:
go run ./cmd/golangorg
The supporting programs cmd/admingolangorg and cmd/googlegolangorg are the servers for admin.golang.org and google.golang.org. (They do not use the _content/ directories.)
Each command directory has its own README.md explaining deployment.
This repository uses eslint to format JS and TS files, and stylelint to format CSS files.
See also:
It is encouraged that all JS, TS, and CSS code be run through formatters before submitting a change. However, it is not a strict requirement enforced by CI.
./npm install./npx eslint [options] [file] [dir]
./npx stylelint [input] [options]
TypeScript files served from _content are transformed into JavaScript. Reference .ts files in html templates as module code.
<script type="module" src="/ts/filename.ts">
Write unit tests for TypeScript code using the jest testing framework.
./npx jest [TestPathPattern]
Each time a CL is reviewed and submitted, the code is deployed to App Engine. See cmd/golangorg/README.md for details.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://go.dev/doc/contribute.
The git repository is https://go.googlesource.com/website.
The main issue tracker for the website repository is located at https://go.dev/issues. Prefix your issue with “x/website:” in the subject line, so it is easy to find.