зеркало из https://github.com/golang/build.git
7478086087
The check was added for golang/go#34045, back when doc/contrib.html lived in the main repo and needed to be manually updated before each major Go release. This is no longer applicable after CL 229483 and CL 229485, so remove it before the upcoming Go 1.15 release. This is compatible with future major releases and does not affect upcoming minor releases of previous major releases. Fixes golang/go#40476. Updates golang/go#34045. Change-Id: Ifc54dce106633e3d6b9ccdb0db4dae2b7434ce93 Reviewed-on: https://go-review.googlesource.com/c/build/+/245477 Reviewed-by: Carlos Amedee <carlos@golang.org> |
||
|---|---|---|
| .. | ||
| README.md | ||
| gcs.go | ||
| git.go | ||
| github.go | ||
| http.go | ||
| main.go | ||
| markdown.go | ||
README.md
golang.org/x/build/cmd/releasebot
Command releasebot runs a Go release.
The release happens in two stages:
- the
preparestage checks preconditions, makes the release commit and mails it for review (if applicable), and performs testing; - the
releasestage runs after the release commit (if any) is merged, and it tags, builds and cleans up the release.
Permissions
The user running a release will need:
- A GitHub personal access token with the
public_reposcope in~/.github-issue-token, and an account with write access to golang/go - gomote access and a token in your name
- gcloud application default credentials, and an account with GCS access to golang-org for bucket golang-release-staging
release-managergroup membership on Gerrit
NOTE: all but the Gerrit permission are ensured by the bot on startup.