commit | 995577f14f28bed40e5f61132f1b78adbdbbb3d9 | [log] [tgz] |
---|---|---|
author | Jamal Carvalho <jamal@golang.org> | Fri Dec 24 00:36:24 2021 +0000 |
committer | Jamal Carvalho <jamalcarvalho@google.com> | Tue Jan 04 19:30:38 2022 +0000 |
tree | a1fa17f2bbd3083d4f9c663fb2fbf4ef1fbc0983 | |
parent | b24dbb62cf4ad1477dbeb2308e09813f7b2f7fd9 [diff] |
internal/screentest: add support for writing test output to GCS Test scripts parse output locations that begin with gs:// as Cloud Storage buckets. When a bucket is used diff images and cached screenshots are written to and read from GCS objects. Change-Id: I985ccf301ada1bfde82e4e61e1ddf724a824fcb6 Reviewed-on: https://go-review.googlesource.com/c/website/+/373720 Run-TryBot: Jamal Carvalho <jamal@golang.org> Trust: Jamal Carvalho <jamalcarvalho@google.com> Reviewed-by: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.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.
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.