Re: Doc: CG: add instructions for staging branch (issue 5440080)

[k-ohara5a5a]

Putting commits on the local master branch is inviting an accidental
push directly to origin/master.  Assume instead that developers have
their work on some other branch and merge it to stable before pushing.


http://codereview.appspot.com/5440080/diff/1/Documentation/contributor/source-code.itexi
File Documentation/contributor/source-code.itexi (right):

http://codereview.appspot.com/5440080/diff/1/Documentation/contributor/source-code.itexi#newcode1696
Documentation/contributor/source-code.itexi:1696:
Assuming your work is on branch @code{pq} do:
git checkout staging
git pull -r
git merge pq
git push origin staging

http://codereview.appspot.com/5440080/diff/1/Documentation/contributor/source-code.itexi#newcode1697
Documentation/contributor/source-code.itexi:1697: You will not see your
patch on @code{master} until some automatic
on @code{origin/master}

http://codereview.appspot.com/5440080/diff/1/Documentation/contributor/source-code.itexi#newcode1700
Documentation/contributor/source-code.itexi:1700: been lost.  Note that
you can check the commits on @code{staging}
on @code{origin/staging}

http://codereview.appspot.com/5440080/