Git

Trees, Branches, and Blobs

git init
git add *
git commit -m 'hello git'

git init

git clone git://...

tracked/untracked "staged"

file status lifecycle, p. 20 gitbok

git status

Add a file called ".gitignore" to ignore "temporary" or other files you don't want to track.

*.[oa]
*~
*.pyc

git diff

Shows changes to unstaged files only

git diff --cached

Show what you've staged so far

git commit -m 'added new quote'

git commit -a -m 'edited links'

Stages every file (that's being tracked) -- ie "auto add"

git commit --amend

Add forgotten changes to last commit.

git rm readme.txt

git rm --cached readme.txt

Remove from the stage, but not the file! (untrack)

git mv

(technically git "sees" these movements already, same as mv, remove, add: but the command is there for convenience)

git log

git log -p -2

git log --stat

git log --pretty=oneline

git log --graph

git remote

git remote -v

git add remote remote-name URL

Where remote-name is whatever you want it to be called, and the URL is a remote git URL.

git remote show origin

git fetch remote-name

pull = fetch + merge

git push [remote-name] [branch-name]

git push origin master

contrib/completion/git-completion.bash

Add to .bashrc:

source ~/.git-completion.bash

(or)

cp git-completion.bash /etc/bash_completion.d/

(linux)

cp git-completion.bash /opt/local/etc/bash_completion.d/

(mac)

git checkout -b iss53

create + checkout a branch, short for:

git branch iss53
git checkout iss53

git checkout master

git checkout -b fix
git commit -a -m 'fixed something'

git checkout master
git merge fix
git branch -d fix

"Fast-forward" reflects that the changes were "upstream" of the current working state.

Generally, you want to commit all your changes before switching branches (checkout)

If we each write to master -- lots of conflicts? Contrast with creating branch for each person ?!