commit | 42c7c5d75857a7a7a980c96759939e5289fe35ac | [log] [tgz] |
---|---|---|
author | Jonathan Amsterdam <jba@google.com> | Fri Nov 03 17:41:24 2023 -0400 |
committer | Jonathan Amsterdam <jba@google.com> | Fri Nov 10 12:12:18 2023 +0000 |
tree | 1f4ee4336e3bde53f792e1472c315323ae8fa198 | |
parent | 91adbeedb93b065c8ddc40793904c26013f26497 [diff] |
cmd/screentest,internal/screentest: add flag to run subset of tests Add a -run flag to screentest, similar to the one for `go test`, so the user can run only one or a few tests. I found this useful when converting release notes to markdown. Change-Id: I13efe9c5e95b4c939ce8d1b9442f723d51c04e05 Reviewed-on: https://go-review.googlesource.com/c/website/+/539497 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Jonathan Amsterdam <jba@google.com> 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 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">
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.