Hi Sarvi,
I have merged your pull request. In the future please cleanup the pull request so that there is only one commit. Makes it easier to track things. Also, you should create a separate branch for each pull request.
Here is a quick overview of how to do this (as I am also not a git expert, I hope someone can correct me if there is better way):
First add upstream:
$ git remote add upstream g...@github.com:pyjs/pyjs.git
Create a branch from which you'll create a pull request:
$ git checkout -b branch_for_my_future_pull_request upstream/master
The last part will use upstream/master as the basis for your branch. This will produce a cleaner pull request and reduce conflicts.
Then either make your changes in this branch or merge stuff from another branch, etc.
When you are done, first push your branch to your own fork:
$ git push origin branch_for_my_future_pull_request
You can then also merge this branch into your own master:
$ git checkout master
$ git merge branch_for_my_future_pull_request
Github actually promotes this kind of thing because when you push that branch to your own fork and then login to github it will automatically suggest that you push your new branch to upstream/master.
After your pull request has been merged into upstream/master you can delete it.
$ git push origin :branch_for_my_future_pull_request
There is another benefit to doing things this way.
It will allow you to:
1. Continue to add things to your branch after you have created the pull request independent of any other work you're doing.
2. Allow you to have your own private master independent of upstream/master.
Thank you for all your contributions Sarvi!
- lex