Revision of GIT guide from Fri, 02/27/2015 - 09:08

Here are the essential commands for an occasional developer.

git clone git@github.com:OpenMx/OpenMx.git

Clone grabs a copy of the history. You only do this once.
Make some changes. Commit them with

git commit -a

Here are some guidelines about writing a good commit message. After you test your changes and are ready to publish to the rest of the team then

git fetch origin   # fetch any new commits from other developers
git rebase origin/master  # put your changes on top of HEAD
git push origin HEAD:master    # publish your changes

I do not recommend 'git pull'. The user interface for 'pull' is designed for change integrators (think Torvolds), not so much for developers. There is a way to get the same effect as fetch/rebase using pull, but I recommend you do these operations as separate steps.