##// END OF EJS Templates
Return command to the next prompt if help was called halfway through a command. Also, ? at the end of a comment should not trigger help.
Return command to the next prompt if help was called halfway through a command. Also, ? at the end of a comment should not trigger help.

File last commit:

r2599:aa4014be
r4080:dc1dc930
Show More
forking_hell.txt
33 lines | 1.1 KiB | text/plain | TextLexer
Fernando Perez
Add Git workflow docs from Gitwash....
r2599 .. _forking:
==========================================
Making your own copy (fork) of ipython
==========================================
You need to do this only once. The instructions here are very similar
to the instructions at http://help.github.com/forking/ - please see that
page for more detail. We're repeating some of it here just to give the
specifics for the ipython_ project, and to suggest some default names.
Set up and configure a github_ account
======================================
If you don't have a github_ account, go to the github_ page, and make one.
You then need to configure your account to allow write access - see the
``Generating SSH keys`` help on `github help`_.
Create your own forked copy of ipython_
=========================================
#. Log into your github_ account.
#. Go to the ipython_ github home at `ipython github`_.
#. Click on the *fork* button:
.. image:: forking_button.png
Now, after a short pause and some 'Hardcore forking action', you
should find yourself at the home page for your own forked copy of ipython_.
.. include:: git_links.txt