@@ -199,22 +199,15 @@ then submit a "pull request" (PR):
199
199
$ git clone git@github.com:YourLogin/scikit-learn.git
200
200
$ cd scikit-learn
201
201
202
- 4. Install library in editable mode::
203
-
204
- $ pip install --editable .
205
-
206
- for more details about advanced installation, see the
207
- :ref:`install_bleeding_edge` section.
208
-
209
- 5. Create a branch to hold your development changes::
202
+ 4. Create a branch to hold your development changes::
210
203
211
204
$ git checkout -b my-feature
212
205
213
206
and start making changes. Always use a ``feature`` branch. It's good practice to
214
207
never work on the ``master`` branch!
215
208
216
- 6 . Develop the feature on your feature branch on your computer, using Git to do the
217
- version control. When you're done editing, add changed files using ``git add ``
209
+ 5 . Develop the feature on your feature branch on your computer, using Git to do the
210
+ version control. When you're done editing, add changed files using ``git add ``
218
211
and then ``git commit `` files::
219
212
220
213
$ git add modified_files
@@ -224,17 +217,12 @@ then submit a "pull request" (PR):
224
217
225
218
$ git push -u origin my-feature
226
219
227
- 7 . Follow `these
220
+ 6 . Follow `these
228
221
<https://help.github.com/articles/creating-a-pull-request-from-a-fork> `_
229
222
instructions to create a pull request from your fork. This will send an
230
223
email to the committers. You may want to consider sending an email to the
231
224
mailing list for more visibility.
232
225
233
- .. note ::
234
-
235
- If you are modifying a Cython module, you have to re-run step 4 after modifications
236
- and before testing them.
237
-
238
226
.. note ::
239
227
240
228
In the above setup, your ``origin `` remote repository points to
0 commit comments