aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDmitri Shuralyov <dmitshur@golang.org>2021-07-13 17:47:13 -0400
committerDmitri Shuralyov <dmitshur@golang.org>2021-07-13 22:45:26 +0000
commitc3b47cb598e1ecdbbec110325d9d1979553351fc (patch)
tree0c6fb45e38ac1836962a0a96fabc44ed70fdf3a7
parentddfd72f7d10a40a87513a320dae8c52b6dfdb778 (diff)
downloadgo-c3b47cb598e1ecdbbec110325d9d1979553351fc.tar.gz
go-c3b47cb598e1ecdbbec110325d9d1979553351fc.zip
[release-branch.go1.17] update codereview.cfg for release-branch.go1.17
The initial "branch: master" configuration was inherited from when the release-branch.go1.17 branch was branched off the master branch. Update the "branch" key, otherwise a modern git-codereview will mail CLs to the wrong branch. We can set "parent-branch" so that 'git codereview sync-branch' works to merge latest master into release-branch.go1.17, something we want to do for subsequent RCs, maybe up to the final release. (At some point the release freeze will end and tree will open for Go 1.18 development, so we'll be switching to using cherry-picks only. Having parent-branch will not be useful then, but I think harmless.) Change-Id: I36ab977eaeb52bc0a84cc59e807572054f54c789 Reviewed-on: https://go-review.googlesource.com/c/go/+/334376 Reviewed-by: Cherry Mui <cherryyz@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> Trust: Dmitri Shuralyov <dmitshur@golang.org>
-rw-r--r--codereview.cfg3
1 files changed, 2 insertions, 1 deletions
diff --git a/codereview.cfg b/codereview.cfg
index 77a74f108e..9d5ebe82eb 100644
--- a/codereview.cfg
+++ b/codereview.cfg
@@ -1 +1,2 @@
-branch: master
+branch: release-branch.go1.17
+parent-branch: master