aboutsummaryrefslogtreecommitdiffstats
path: root/docs/content
diff options
context:
space:
mode:
authorTay Ray Chuan2013-07-05 12:34:55 +0800
committerPawel Kozlowski2013-07-10 22:18:44 +0200
commit220f0dbcf11ef8bba8917e9a7f5877b49bedb4e9 (patch)
tree6f13026419c3696443d906868ea05f906a942cb4 /docs/content
parent899f5d14574c4b79508bc8432fab74523c076a70 (diff)
downloadangular.js-220f0dbcf11ef8bba8917e9a7f5877b49bedb4e9.tar.bz2
docs(contribute): improve git instructions
Diffstat (limited to 'docs/content')
-rw-r--r--docs/content/misc/contribute.ngdoc18
1 files changed, 7 insertions, 11 deletions
diff --git a/docs/content/misc/contribute.ngdoc b/docs/content/misc/contribute.ngdoc
index 8b6a7627..7cae67c3 100644
--- a/docs/content/misc/contribute.ngdoc
+++ b/docs/content/misc/contribute.ngdoc
@@ -256,31 +256,27 @@ To create and submit a change:
[print, sign and one of scan+email, fax or mail the form](http://code.google.com/legal/corporate-cla-v1.0.html).
-2. Create a new branch off the master for your changes:
+2. Create and checkout a new branch off the master branch for your changes:
- git branch my-fix-branch
+ git checkout -b my-fix-branch master
-3. Check out the branch:
+3. Create your patch, make sure to have plenty of tests (that pass).
- git checkout my-fix-branch
-
-4. Create your patch, make sure to have plenty of tests (that pass).
-
-5. Commit your changes and create a descriptive commit message (the commit message is used to generate release notes,
+4. Commit your changes and create a descriptive commit message (the commit message is used to generate release notes,
please check out our
[commit message conventions](https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit#)
and our commit message presubmit hook `validate-commit-msg.js`):
git commit -a
-6. Push your branch to Github:
+5. Push your branch to Github:
git push origin my-fix-branch
-7. In Github, send a pull request to `angular:master`.
+6. In Github, send a pull request to `angular:master`.
-8. When the patch is reviewed and merged, delete your branch and pull yours — and other — changes
+7. When the patch is reviewed and merged, delete your branch and pull yours — and other — changes
from the main (upstream) repository:
1. To delete the branch in Github, run: