| commit | 6244401143db649bfa09234e4b0e4db1b40b8ec3 | [log] [tgz] |
|---|---|---|
| author | Russ Cox <rsc@golang.org> | Thu Jan 07 21:14:22 2021 -0500 |
| committer | Russ Cox <rsc@golang.org> | Wed Jan 13 09:36:16 2021 -0500 |
| tree | c196f7ba683ef1920535bbc5bb2842266179cb61 | |
| parent | bc5a6b70306f5512d03ea7ddb2da996887092555 [diff] |
git-codereview: add sync-branch -merge-back-to-parent Dev branches come to an end. Making sync-branch help that process instead of forcing people to follow a playbook will help avoid mistakes. The flag name was chosen to be very unlikely to be used accidentally, and the commit subject and message both are distinct to make clear to reviewers what they are being asked to +2. The Merge List is also included in full and is likely to be quite large, yet another signal for everyone involved about the magnitude and weight of the change. Change-Id: I91cdda2b85cd3811711a339f4f3290fee109022e
The git-codereview tool is a command-line tool for working with Gerrit.
The easiest way to install is to run go get -u golang.org/x/review/git-codereview. You can also manually git clone the repository to $GOPATH/src/golang.org/x/review.
Run git codereview hooks to install Gerrit hooks for your git repository.
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 review repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/review:” in the subject line, so it is easy to find.