|author||Dmitri Shuralyov <email@example.com>||Fri May 13 19:06:47 2022 -0400|
|committer||Gopher Robot <firstname.lastname@example.org>||Fri May 13 23:12:24 2022 +0000|
internal/short: include invalid input in error If the input is invalid, it generally helps to see it (including any invisible characters as printed by %q) in the error message. Do that. Change-Id: Ibe179a7c03c29b1caa0532aff08cee1b11fbb051 Reviewed-on: https://go-review.googlesource.com/c/website/+/406354 TryBot-Result: Gopher Robot <email@example.com> Run-TryBot: Dmitri Shuralyov <firstname.lastname@example.org> Auto-Submit: Dmitri Shuralyov <email@example.com> Reviewed-by: Ian Lance Taylor <firstname.lastname@example.org> Reviewed-by: Dmitri Shuralyov <email@example.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.
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.
./npx eslint [options] [file] [dir]
./npx stylelint [input] [options]
<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 main issue tracker for the website repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/website:” in the subject line, so it is easy to find.