summaryrefslogtreecommitdiff
path: root/doc/source/dev/gitwash/development_workflow.rst
diff options
context:
space:
mode:
authorRalf Gommers <ralf.gommers@googlemail.com>2012-09-22 17:28:19 +0200
committerRalf Gommers <ralf.gommers@googlemail.com>2012-09-22 17:28:19 +0200
commit0dd5a76bcc3da1c3b016a1304bba31c6c55cdeb4 (patch)
tree2800e94ab0278993d12259ee993a69f91a070209 /doc/source/dev/gitwash/development_workflow.rst
parent936fb7c3e2636bfc7f1f9ece72ab37e3df073bba (diff)
downloadnumpy-0dd5a76bcc3da1c3b016a1304bba31c6c55cdeb4.tar.gz
DOC: one more edit to the dev-guide.
Recommend to update master before creating your feature branch. Thanks to Nicky van Foreest for feedback on the dev-guide.
Diffstat (limited to 'doc/source/dev/gitwash/development_workflow.rst')
-rw-r--r--doc/source/dev/gitwash/development_workflow.rst8
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/source/dev/gitwash/development_workflow.rst b/doc/source/dev/gitwash/development_workflow.rst
index fe98fb64d..cf7c26965 100644
--- a/doc/source/dev/gitwash/development_workflow.rst
+++ b/doc/source/dev/gitwash/development_workflow.rst
@@ -16,7 +16,8 @@ Basic workflow
In short:
-1. Start a new *feature branch* for each set of edits that you do.
+1. Update your ``master`` branch if it's not up to date.
+ Then start a new *feature branch* for each set of edits that you do.
See :ref:`below <making-a-new-feature-branch>`.
Avoid putting new commits in your ``master`` branch.
@@ -78,6 +79,11 @@ as clear as possible.
Making a new feature branch
===========================
+To update your master branch, use::
+
+ git fetch upstream
+ git merge upstream/master --ff-only
+
To create a new branch and check it out, use::
git checkout -b my-new-feature upstream/master