@@ -52,13 +52,12 @@ and help you to craft the change so that it is successfully accepted into the pr
52
52
53
53
1 ) Create a fork of AngularFire (See [ Forking a Project] [ github-fork ] )
54
54
55
- 2 ) CD into your clone and install dependencies
55
+ 2 ) Clone your fork, CD into the directory, and install dependencies
56
56
57
57
``` shell
58
- $ git clone
59
- $ npm install
60
- $ npm run build
61
- $ npm test
58
+ $ git clone < your fork SSH/HTTPS from GitHub>
59
+ $ yarn install
60
+ $ yarn test
62
61
```
63
62
64
63
3 ) Make your changes in a new git branch:
@@ -105,8 +104,7 @@ You can file new issues by providing the above information [here](https://github
105
104
106
105
* Create your patch, ** including appropriate test cases** .
107
106
* Follow the [ Angular Coding Rules] [ rules ] .
108
- * Run the full test suite, as described in the [ developer documentation] [ dev-doc ] ,
109
- and ensure that all tests pass.
107
+ * Run the full test suite (` yarn test ` ) and ensure that all tests pass.
110
108
* Commit your changes using a descriptive commit message that follows the
111
109
[ Angular commit message conventions] [ commit ] . Adherence to these conventions
112
110
is necessary because release notes are automatically generated from these messages.
@@ -135,24 +133,6 @@ You can file new issues by providing the above information [here](https://github
135
133
136
134
That' s it! Thank you for your contribution!
137
135
138
- #### <a name="submit-docs"></a> Deploying Docs
139
-
140
- 1) Build the docs
141
-
142
- `$ npm run docs`
143
-
144
- 2) Deploy Docs to Firebase Hosting
145
-
146
- (Ask @jeffbcross to add you as a collaborator or deploy on your behalf)
147
-
148
- ```
149
- $ npm install -g firebase-tools
150
- $ firebase login
151
- $ npm run docs
152
- $ cd docs
153
- $ firebase deploy
154
- ```
155
-
156
136
## <a name="cla"></a> Signing the CLA
157
137
158
138
Please sign our Contributor License Agreement (CLA) before sending pull requests. For any code
0 commit comments