OpenHatch git workflow

Some guidelines on how to use git when working on OpenHatch

= Getting a new clone of OpenHatch = Only need to do this once. Or if you want to start form scratch. It is also good (okay) to remove your  directory and start over if you aren't sure the state of your OpenHatch repository.

= Committing a patch =
 * 1) After you have already retreived your respository of code and made some changes, now you need to submit your changes for review to OpenHatch.
 * 2)  (make sure the right files are listed here)
 * 3) Note: If you want to submit everything listed in 'Unstaged changes' in, you can just do  , and skip the previous two steps.
 * 4)  (opens in less editor)
 * 5) Note: This is just to help you verify that your commit took effect correctly. If it didn't, there were likely errors in one or more of the above steps.
 * 6) Now fetch any updates that may have occurred since you last did a  or a
 * 7) Note: This is just to help you verify that your commit took effect correctly. If it didn't, there were likely errors in one or more of the above steps.
 * 1) Now fetch any updates that may have occurred since you last did a  or a
 * 2) Note: This is just to help you verify that your commit took effect correctly. If it didn't, there were likely errors in one or more of the above steps.
 * 1) Note: This is just to help you verify that your commit took effect correctly. If it didn't, there were likely errors in one or more of the above steps.
 * 1) Note: This is just to help you verify that your commit took effect correctly. If it didn't, there were likely errors in one or more of the above steps.
 * 1) Note: This is just to help you verify that your commit took effect correctly. If it didn't, there were likely errors in one or more of the above steps.
 * 1) Note: This is just to help you verify that your commit took effect correctly. If it didn't, there were likely errors in one or more of the above steps.

= Submitting a patch = Find your patch file that has been generated from the  command. In your current directory you can run which will list your files in time-sort order. Listing the newest modified files at the bottom. Look for the file similar to . This file or these files will need to be added to the bug tracker... if we are still doing this. The alternative is just using github, which some people are starting to look into.

= Other useful commands =
 * -- to combine patches into one. after which re-run format-patch command. notice "-i"

= Resources =
 * http://gitref.org/
 * http://git-scm.com/documentation

= See also =
 * How to generate patches with git format-patch
 * How we handle patches