081156a208
The main point of Website-Publish+1 was to manually avoid a race in Cloud Build when multiple commits land. But now cmd/locktrigger takes care of that race automatically, so there is little point to Website-Publish+1 now. Stop looking for it. (If a commit landed without Website-Publish+1, it would still be published with the next Website-Publish+1 commit, so it was no real restriction on who can publish content.) I considered adding a rule like "DO NOT PUBLISH" in a commit message means not to publish the commit, but once it lands, again the next publishable commit is going to publish all previous commits, so even the possibility of landing such commits puts the repo in a very fragile state. Better not to support that idea at all. Fixes golang/go#36707. Change-Id: Icfe3bcdb0003608ff84bb300c43b61b542236571 Reviewed-on: https://go-review.googlesource.com/c/website/+/368366 Trust: Russ Cox <rsc@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> |
||
|---|---|---|
| _content | ||
| _later/security | ||
| cmd | ||
| internal | ||
| tour | ||
| .eslintrc.json | ||
| .gitattributes | ||
| .prettierrc | ||
| .prettierrc.yaml | ||
| .stylelintrc.json | ||
| AUTHORS | ||
| CONTRIBUTING.md | ||
| CONTRIBUTORS | ||
| LICENSE | ||
| PATENTS | ||
| README.md | ||
| codereview.cfg | ||
| content.go | ||
| go-app-deploy.sh | ||
| go.mod | ||
| go.sum | ||
README.md
Go website
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.
JS/CSS Formatting
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.
Deploying
Each time a CL is reviewed and submitted, the code is deployed to App Engine. See cmd/golangorg/README.md for details.
Report Issues / Send Patches
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.