<commit_before>.. _follower-to-developer:

==================================================
 Changing from following the code, to development
==================================================

Private edits, keeping track of upstream development
====================================================

Overview
--------

::
       
   # make new branch
   git branch my-edits
   git checkout my-edits
   # hack hack
   git commit -am 'My edits in my branch'
   # update your branch from upstream
   git pull origin/master

Keeping a github_ copy of your private edits
============================================

Overview
--------

#. make a github_ account
#. tell git_ who you are
#. fork *nipy* repository using github_ interface

Then::

   # remove read-only pointer to upstream repository
   git remote rm origin
   # add pointer to your own fork
   git remote add origin git<EMAIL>:you-user-name/nipy.git
   # add back renamed read-only pointer to upstream
   git remote add mainline git://github.com/gitwash/nipy.git
   # push your branch to github
   git checkout my-edits
   git push origin my-edits

Details
-------

Make a github_ account
~~~~~~~~~~~~~~~~~~~~~~

.. include:: make_account.txt

Tell git_ who you are
~~~~~~~~~~~~~~~~~~~~~

.. include:: set_user.txt

Make a forked copy of nipy
~~~~~~~~~~~~~~~~~~~~~~~~~~

.. include:: make_fork.txt





Making a patch
==============

Overview
--------

some text


.. include:: links_names.txt<commit_msg>More unpacking<commit_after>.. _follower-to-developer:

==================================================
 Changing from following the code, to development
==================================================

Private edits, keeping track of upstream development
====================================================

Overview
--------

::
       
   # make new branch
   git branch my-edits
   git checkout my-edits
   # hack hack
   git commit -am 'My edits in my branch'
   # update your branch from upstream
   git pull origin/master

Keeping a github_ copy of your private edits
============================================

Overview
--------

#. make a github_ account
#. tell git_ who you are
#. fork *nipy* repository using github_ interface

Then::

   git remote rm origin
   git remote add origin <EMAIL>:your-user-name/nipy.git
   git remote add mainline git://github.com/gitwash/nipy.git
   git push origin my-edits

Details
-------

Make a github_ account
~~~~~~~~~~~~~~~~~~~~~~

.. include:: make_account.txt

Tell git_ who you are
~~~~~~~~~~~~~~~~~~~~~

.. include:: set_user.txt

Make a forked copy of nipy
~~~~~~~~~~~~~~~~~~~~~~~~~~

.. include:: make_fork.txt

Link your local branch to github
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Git uses the ``origin`` name to point to the main home of this
repository.  You want to set this to be your forked copy.

First, delete the current ``origin`` link, because that points to the
main *nipy* repository::

   git remote rm origin

Next make ``origin`` point to your new forked copy::

   git remote add origin <EMAIL>:your-user-name/nipy.git

Add back the reference to the main *nipy* repository, but with another
name::

   git remote add mainline git://github.com/gitwash/nipy.git

Next push your own branch into your own github copy of *nipy*::

   git push origin my-edits


Making a patch
==============

Overview
--------

some text


.. include:: links_names.txt
{'fraction_non_alphanumeric': 0.24653902798232696, 'fraction_numerical': 0.0, 'mean_word_length': 3.6970954356846475, 'pattern_counts': {'":': 0, '<': 6, '<?xml version=': 0, '>': 6, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2859164', 'n_tokens_mistral': 965, 'n_tokens_neox': 869, 'n_words': 357}