commit | f5c5fdde3f381ce1a239827afdc78c6315c94f67 | [log] [tgz] |
---|---|---|
author | Jamal Carvalho <jamal@golang.org> | Sat Jan 08 20:38:24 2022 +0000 |
committer | Jamal Carvalho <jamalcarvalho@google.com> | Mon Jan 10 20:33:13 2022 +0000 |
tree | 9b080b39a03ac926ce5369d6f80d61af98a46bcc | |
parent | b3dd1e39e5b9bb5d232b2756ac3f99afb1c775fa [diff] |
internal/screentest: fix safe extension collection Previously, obsolete screenshots would only be cleared if the cache was enabled. This change ensures all obsolete screenshots are deleted prior to running tests. Change-Id: If37caf92446f2174ef293177e9924f61a167cb81 Reviewed-on: https://go-review.googlesource.com/c/website/+/377255 Run-TryBot: Jamal Carvalho <jamal@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Trust: Jamal Carvalho <jamalcarvalho@google.com> Reviewed-by: Jonathan Amsterdam <jba@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 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">
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.