go.dev: make cloudbuild.yaml safe to run in golang-org project

Setting --project=go-discovery on the command lines is enough
to do the deploy directly from golang-org Cloud Build, avoiding
an inline cloudbuild.yaml in the trigger configuration that was
reinvoking the cloud build in the other project.

(I gave the golang-org cloud build account permission to be an
"App Engine Deployer" for go-discovery.)

Change-Id: Iafed260f96b9adcf7442a9fa0df2cc44ea28a2ea
Reviewed-on: https://go-review.googlesource.com/c/website/+/328690
Trust: Russ Cox <rsc@golang.org>
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Go Bot <gobot@golang.org>
Reviewed-by: Jamal Carvalho <jamal@golang.org>
1 file changed
tree: c31982ce09c8541bf50cb438c7c317ac29c15bf0
  1. .gitattributes
  2. .prettierrc
  3. AUTHORS
  4. CONTRIBUTING.md
  5. CONTRIBUTORS
  6. LICENSE
  7. PATENTS
  8. README.md
  9. _content/
  10. blog/
  11. cmd/
  12. codereview.cfg
  13. content.go
  14. go-app-deploy.sh
  15. go.dev/
  16. go.mod
  17. go.sum
  18. internal/
  19. tour/
README.md

Go website

Go Reference

This repo holds content and serving programs for the golang.org web site.

Content is in _content/. Server code is in cmd/ and internal/.

To run the 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/ directory.)

Each command directory has its own README.md explaining deployment.

JS/CSS Formatting

This repository uses prettier to format JS and CSS files.

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.

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.

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.