Forkin and Pushin

working tree - your unstaged files
index - staged files
snapshot - in source control

git status -s

git log

 see hash of snapshot contents. each commit get new hash, usually can abbreviate hash using first 7 chars of the hash

git show <hash>

git gui

git log --pretty=raw or oneline

https://gist.github.com/ralfebert/515937

git checkout restores the files from the index

git diff 7char1...7char2 or git log -p

git tag labelname1 7char1 gives a tag to a commit

use a branch to create changes seperate from our main changes (i.e. master)

branch is a label to a commit - git branch -v

git branch newfeature creates a branch

switch between branches using git checkout <branchname>

if you are positioned on master you can do git merge newfeaure

gitk can be entered at command prompt

remotes is connection from one git repository to another

git remote -v shows connections

push your master to git hub (i.e. origin) : git push -u origin master

merging happens automatically when pulling from remote

In GitHub , What is a Fork

At some point you may find yourself wanting to contribute to someone else's project, or would like to use someone's project as the starting point for your own. This is known as "forking"

[more]

https://help.github.com/articles/using-pull-requests

Pull requests let you tell others about changes you've pushed to a GitHub repository. Once a pull request is sent, interested parties can review the set of changes, discuss potential modifications, and even push follow-up commits if necessary.

There is the git-flow . See talk