1. GETTING GIT
…before it gets you

2. HOW TO BE GOTTEN
 I am ‘notmessenger’ in most networks and
notmessenger.com/contact has the rest of the ways to find me

4. WHAT IS IT?

5. IT’S THE NEW HOTNESS!
 Source code management system
 Version control
 and …. Distributed!

6. DISTRIBUTED?
 There is no central server where your repository must be
maintained
 Also referred to as being “Decentralized”
 Everything you need to maintain a repository is already on your
local machine (once you have installed Git)

7. KEY CONCEPTS

8. REMEMBER THESE!
 Distributed
 Staging Area
 …or Index
 …or Cache
 …or Directory cache
 …or Current directory cache
 …or Staged files

9. STAGING AREA

10. WHERE GIT EXCELS

11. MORE AWESOMENESS!
 Branches
 Merging
 Stashes

12. COMMANDS

13. INIT
 Create a new repository
 Can be empty directory
 Can be existing codebase
 Example:
> git init

14. CONFIG
 Manage configuration
 Example:
> git config --global user.name ‘Jeremy Brown’
> git config --global user.email ‘jeremy@notmessenger.com’

15. STATUS
 Display the state of your codebase
 Has anything been modified or staged since the last commit?
 Example:
> git status

16. DIFF
 Show diff between states of codebase
 Example:
> git diff <filename>

17. ADD
 Start tracking new files
 Stage changes to already-tracked files
 Example:
> git add .
> git add NEWFILE
> git add ALREADY_EXISTENT_FILE

18. COMMIT
 Record the snapshot of your staged content
 Example:
> git commit
> git commit -m “Commit message”
> git commit -a
> git commit -am “Commit message”

19. LIVE DEMO

20. COLLABORATION

21.  Git doesn’t have a central server, such as how SVN or others do
 You collaborate by synchronizing with other repositories
 There is no real difference between a server and client – a Git
repository is a Git repository and you can synchronize between
any two easily

22. MORE COMMANDS

23. CHECKOUT
 Checkout a branch from a remote repository to working directory
 Example:
> git checkout <branchname>

24. FETCH
 Download new branches and data from a remote repository
 Is a separate copy of the data from the remote repository – it is
not merged with your local working copy
 Can then look through new commits, view logs, etc
 Example:
> git fetch
> git fetch [alias]
> git fetch --all

25. PULL
 First issues a FETCH command and then a MERGE command
 Example:
> git pull
> git pull [alias]
> git pull --all

26. PUSH
 Push your new branches and data to a remote repository
 If someone else has pushed since the last time you fetched and
merged the Git server will deny your push until you are up to date
 Example:
> git push [alias] [branch]

27. REMOTE
 List, add and delete remote repository aliases
 Example:
> git remote
> git remote add [alias] [url]
> git remote rm [alias]

28. BRANCH
 List, create or delete branches
 Example:
> git branch
> git branch <branchname>
> git branch –d <branchname>

29. MERGE
 Merge any branch into the current branch
 Example:
> git merge <branchname>
> git merge --no-commit <branchname>

30. STASH
 Takes the dirty state of your working directory and saves it on a
stack of unfinished changes that you can reapply at any time
 Example:
> git stash
> git stash list
> git stash apply <stashname>
> git stash drop <stashname>

31. LIVE DEMO

32. GUI TOOLS

33. MAKE YOUR LIFE EASIER
 GitHub for Mac/Windows/Eclipse/Mobile
 Git Tower
 Gitbox
 GitX
 SmartGit

34. DEMO OF GIT TOWER

35. CODE MANAGEMENT
STRATEGIES

37. HOW IS GIT GOING TO GET
YOU?

38. LOOKOUT!
 A few of the differences between it and previous generations of
SCMs
 The index (or stage)
 Distributed
 Commit history
 Git is the new hotness and is being used (virtually) everywhere

39. GOT IT?

40. RESOURCES
 git-scm.com
 git-tower.com
 github.com/nvie/gitflow

41. IMAGE CREDITS
 Slide 1 - joecrazy.com/wp-content/uploads/2012/05/14.jpg
 Slide 5 - jpegy.com/images/uploads/2012/03/battleshots.jpg
 Slide 9 - learn.github.com/images/staging.png
 Slide 11 - moustachemadness.files.wordpress.com/2012/02/handlebar-
moustache.jpg