Generally, you will want to keep this also on your public github fork
of ipython. To do this, you git push this new branch up to your github
repo. Generally (if you followed the instructions in these pages, and
by default), git will have a link to your github repo, called
origin. You push up to your own repo on github with:

git push origin my-new-feature

From now on git will know that my-new-feature is related to the
my-new-feature branch in the github repo.

Add any new files to version control gitaddnew_file_name (see
git add).

To commit all modified files into the local copy of your repo,, do
gitcommit-am'Acommitmessage'. Note the -am options to
commit. The m flag just signals that you’re going to type a
message on the command line. The a flag - you can just take on
faith - or see why the -a flag?. See also the git commit manual
page.

To push the changes up to your forked repo on github, do a gitpush (see git push).

The generated comparison, is between your feature branch
my-new-feature, and the place in master from which you branched
my-new-feature. In other words, you can keep updating master
without interfering with the output from the comparison. More detail?
Note the three dots in the URL above (master...my-new-feature) and
see Two and three dots in difference specs.