From: Leigh McCulloch Date: Sat, 4 Nov 2017 20:54:30 +0000 (+0000) Subject: doc: move single change workflow note in contribution guide X-Git-Tag: go1.10beta1~106 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=07a2ffaf0b2961c76e69e3ca910b6a08a687626b;p=gostls13.git doc: move single change workflow note in contribution guide The note about the single change workflow is included in the git-codereview installation instructions, but it has nothing to do with installing git-codereview. This note is more relevant for when a change is actually being made. Change-Id: Iccb90f3b7da87fab863fa4808438cd69a21a2fce Reviewed-on: https://go-review.googlesource.com/76317 Reviewed-by: Steve Francia --- diff --git a/doc/contribute.html b/doc/contribute.html index 085e9c60d9..b35e9f4b18 100644 --- a/doc/contribute.html +++ b/doc/contribute.html @@ -208,12 +208,6 @@ daily work, install the hooks in a new Git checkout by running git-codereview hooks.

-

-The workflow described below assumes a single change per branch. -It is also possible to prepare a sequence of (usually related) changes in a single branch. -See the git-codereview documentation for details. -

-

Set up git aliases

@@ -429,6 +423,12 @@ In the Go contribution workflow this is done with a git directly to that local branch.

+

+The workflow described here assumes a single change per branch. +It is also possible to prepare a sequence of (usually related) changes in a single branch. +See the git-codereview documentation for details. +

+
 $ git change <branch>