diff options
| author | Tay Ray Chuan | 2013-07-05 12:34:55 +0800 |
|---|---|---|
| committer | Pawel Kozlowski | 2013-07-10 22:23:12 +0200 |
| commit | 2471f6b01c2fe26269bae53f173921350a8f418d (patch) | |
| tree | f8318377343d28a38049e4af5847595da0da8873 /docs/content | |
| parent | 1fefafd09f5b47fc56e6072e75850c92757b2afd (diff) | |
| download | angular.js-2471f6b01c2fe26269bae53f173921350a8f418d.tar.bz2 | |
docs(contribute): improve git instructions
Diffstat (limited to 'docs/content')
| -rw-r--r-- | docs/content/misc/contribute.ngdoc | 18 |
1 files changed, 7 insertions, 11 deletions
diff --git a/docs/content/misc/contribute.ngdoc b/docs/content/misc/contribute.ngdoc index 0e790f18..66b8b38c 100644 --- a/docs/content/misc/contribute.ngdoc +++ b/docs/content/misc/contribute.ngdoc @@ -247,31 +247,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: |
