|author||Dmitri Shuralyov <email@example.com>||Tue Apr 05 17:19:53 2022 -0400|
|committer||Dmitri Shuralyov <firstname.lastname@example.org>||Tue Apr 05 23:38:44 2022 +0000|
cmd/golangorg: specify region in Cloud Build URLs explicitly The GCP web UI remembers region selection across different visits. If a user picks another region in another context, these links may display a misleading page that doesn't show all intended build history and trigger entries. Explicitly include the region as global (non-regional) in the URL to remove that pitfall and make the links more predictable. Change-Id: Ie540853ef54bcfb253b28c492bbf56b251db28aa Reviewed-on: https://go-review.googlesource.com/c/website/+/398536 Trust: Dmitri Shuralyov <email@example.com> Reviewed-by: Jamal Carvalho <firstname.lastname@example.org>
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.
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.