Gofmt to update doc comments to the new formatting.
For golang/go#51082.
Change-Id: I3573e720b522fe41f726d2fb4e3b988ee883872d
Reviewed-on: https://go-review.googlesource.com/c/website/+/399608
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Ian Lance Taylor <iant@google.com>
When a project uses “continuous deployment powered by Cloud Build”,
the deployment is a little bit too continuous: when multiple commits
land in a short time window, Cloud Build will run all the triggered
build jobs in parallel. If each job does “gcloud app deploy”, there
is no guarantee which will win: perhaps an older commit will complete
last, resulting in the newest commit not actually being the final
deployed version of the site. This should probably be fixed in
“continuous deployment powered by Cloud Build”, but until then,
locktrigger works around the problem.
Use locktrigger in cmd/golangorg/cloudbuild.yaml to ensure that
when multiple commits race, the newest one always runs its
go-app-deploy.sh last.
Change-Id: I5ca340250d0a3b7853fc478d35caffdd0163bb0f
Reviewed-on: https://go-review.googlesource.com/c/website/+/368365
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>
Russ Cox