Who is this for? ● Folks starting to use Git or foraying just now ● Folks who are using SmartGit :) ● Using Git as CVCS http://rogerdudler.github.io/git-guide/
Create a new Repository $ cd project/ $ git init # initializes the repository $ git add . # add those 'unknown' files - ADDS FOR STAGE $ git commit # commit all changes, edit changelog entry - M $ git rm --cached ... # ridiculously complicated command to undo, in case you forgot .gitignore $ git reset HEAD # same as before $ git init project002 #shortcut for mkdir project002 && cd project002 && git init
Git status $ git status # On branch master # # Initial commit # # Changes to be committed: # (use "git rm --cached ..." to unstage) # # new file: README # new file: hello.py # # Changed but not updated: # (use "git add ..." to update what will be committed) # (use "git checkout -- ..." to discard changes in working directory) # # modified: README #
Git add Start tracking new files and also to stage changes to already tracked files $ touch README.md; echo “test” > README.md $ git status $ git add . $ git status $ git diff Shortcut: git commit -a # the -a flag pulls in all modified files will commit all changed files (but not new files, those need to be added to the index with git-add). If you want to commit only certain files then you will need to stage them first with git-add
Git diff To compare two revisions of a file, or your current file and a previous revision $ git diff README.md $ git diff --staged README.md $ git diff HEAD README.md $ git diff --stat README.md To compare 2 revisions of a file: $ git diff
.gitignore $ git add .gitignore will use its rules when looking at files to commit to ignore from staging $ git rm --cached filename will not ignore a file that was already tracked before a rule was added to this file # to remove the tracked file - Caution: This deletes the file $ git config --global core.excludesfile ~/.gitignore_global file can be committed into the repository, thus sharing the rule list with any other users that clone the repository.
Git Commit $ git commit -m 'my awesome changes' -m option not given - open a text editor for you to write your commit message. $ git commit -a automatically stage all tracked, modified files before the commit
Git push remote branches are identical to local branches except that Git will not allow you to check them out. However, you can merge from them, diff them to other branches, run history logs on them, etc. You do all of that stuff locally after you synchronize. $ git push # push new commits to the on the repository For someone coming from CVS, the commit to the central repository now requires two steps. $ git clone # creates a remote called origin for push and fetch
Git reset just a plain old git reset should unstage accidental git add $ git reset --soft undo the last commit and put the files back onto the stage $ git reset --hard undo the last commit, unstage files AND undo any changes in the working dir $ git-reset --hard Revert to a previous commit by hash $ git-reset --hard HEAD^ your last commit before pull/merge
Git reset $ git reset HEAD unstage file and copy from latest commit $ git reset -- unstages specific files and copy files from the stage $ git checkout HEAD -- files copies files from the latest commit to both the stage and the working directory. $ git checkout -- files copies files from the stage to the working directory. Use this to throw away local changes.
git branch The default branch in a git repository is called master. $ git branch To create a new branch use $ git branch To see a list of all branches in the current repository type $ git checkout If you want to switch to another branch you can use $ git checkout -b To create a new branch and switch to it in one step $ git branch -d # To delete a branch $ git stash branch # To create a branch with current changes
git rebase $ git checkout experiment $ git rebase master First, rewinding head to replay your work on top of it... Applying: added staged command $ git rebase -i $ git rebase --interactive
git merge If you want to merge a branch (e.g. master to release), make sure your current branch is the target branch you'd like to merge into (use git branch or git status to see your current branch). $ git merge experiment where experiment is the name of the branch you want to merge with the current branch $ git diff to see pending conflicts you have to resolve. $ git checkout -b linux-work # create a new branch $ $ git commit -a $ git checkout master # go back to master branch $ git merge linux-work # merge changesets from linux-work
git merge $ git checkout master $ git rebase topic First, rewinding head to replay your work on top of it... Fast-forwarded master to topic. This command lays the latest changes to topic right on top of the master branch, and preserves all of your commit history- laying them right on the end of the master branch’s commit history. $ git merge --squash topic This command will result in a commit log like a normal merge- meaning that all of the individual commit messages from the topic branch will become one single “merge” message.
Quick tips $ git log -- filename see the history of revisions to a file $ gitk inspect history visually, shows you how the revisions are connected $ git log this pipes a log of the current branch into your PAGER $ git log -p # same as above, but append a patch after each commit message $ git show HEAD show commit info, diffstat and patch of the tip of current branch
Quick tips $ git filter-branch --tree-filter 'rm -f filename' HEAD remove all instances of a file from every commit $ git filter-branch --env-filter \ "export [email protected]" HEAD change your email in all commits $ git blame history of user changes in a file $ git log --pretty=oneline --graph pretty log with a graph of changes done
sengopal
hirobe1999
kotomin_m
codehex
y0gi
terukinakano
yuya4
o0h
77web
masumitsu
leichteckig
ryunen344
cocoeyes02
dougneiner
pauljervisheath
mojombo
philhawksworth
andyhume
smashingmag
cherdarchuk
brad_frost
holman
jnunemaker
carmenintech
lara