|author||Oleksandr Redko <email@example.com>||Thu Mar 09 13:20:10 2023 +0200|
|committer||Gopher Robot <firstname.lastname@example.org>||Sat Mar 11 12:46:05 2023 +0000|
_content/blog: fix issues in test coverage blog post - Fix typo in GitHub. - Remove duplicated word. - Code blocks must be indented with TAB to render correctly. Change-Id: I71b6962aab1379ceaab71b8747d1457337a2111c Reviewed-on: https://go-review.googlesource.com/c/website/+/474876 TryBot-Result: Gopher Robot <email@example.com> Auto-Submit: Ian Lance Taylor <firstname.lastname@example.org> Reviewed-by: Carlos Amedee <email@example.com> Reviewed-by: Ian Lance Taylor <firstname.lastname@example.org> Run-TryBot: Ian Lance Taylor <email@example.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.
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.