commit | 545eb263a77995c9453c82596c98c39ab2f02beb | [log] [tgz] |
---|---|---|
author | Russ Cox <rsc@golang.org> | Mon Dec 06 15:51:08 2021 -0500 |
committer | Russ Cox <rsc@golang.org> | Mon Dec 06 21:06:05 2021 +0000 |
tree | 6e882b598f1b7ff48fd15f5a12c6c568534637d6 | |
parent | c4713138b04463a93e1ee8e251a1002e0e34debd [diff] |
cmd/locktrigger: fetch directly from Gerrit in unshallow In all my testing with manual triggers using inline cloudbuild.yaml files, git fetch --unshallow had no problems. But now the real trigger is having trouble. Maybe running from an in-repo cloudbuild.yaml has different permissions from inline yaml? Read from Gerrit directly to avoid permission errors. Change-Id: I16436638ad55198973a25ee0395ef77a7430d7c7 Reviewed-on: https://go-review.googlesource.com/c/website/+/369738 Trust: Russ Cox <rsc@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.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 prettier to format JS and CSS files.
See also:
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.
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.