Don't be confused by git. The best way to approach git is through the way we did things in the bad ol' days, by mangling file names and folder structures to make sure we always had a back up.

1. Git-r-done

2. Why Use Git?
- Safety
- History
- Micro-training
- Openess
- Collaboration

3. When Should You Use Git?

4. When Should You Use Git?
Always

5. When Should You Use Git?
Always
CSS, JS, PHP, SASS, Python, etc.

6. When Should You Use Git?
Always
CSS, JS, PHP, SASS, Python, etc.
Anything that has and extension and can
be opened in a text editor

7. Git is not this:

8. Git is not this:

9. Git is not this:

10. Git is not this:

11. The Old Way

12. Have A Copy on a Server

13. Copy To Desktop

14. Save With a New Name

15. Make Some Changes and Save

16. Or Close Without Saving

17. Occasionally We Update
The Final Presentation

18. So We Review Changes

19. Pick The Updates We Like

20. Until Everyone is Synched Up

21. Repeat

22. #Winning

23. That’s All Version Control Is

24. Ok. Back to Git

25. Git is Pretty Much The Same

26. Except Instead of This:

27. Except Instead of This:

28. We See This:

29. Or This:

30. Or This:

31. We Tell Git Which We Want

32. Summarize
Version Control Is:
• Making changes while retaining a master copy
• Having multiple copies of the same file/project
• Saving Changes
• Undoing Changes
• Combining different versions together

33. Command Time!

34. Git Commands
Version Control Is:
• Making changes while retaining a master copy
• Having multiple copies of the same file/project
• Saving changes
• Undoing Changes
• Combining different versions together

35. Git Commands
Version Control Is:
• Making changes while retaining a master copy
• git clone OR git branch
• Having multiple copies of the same file/project
• Saving changes
• Undoing Changes
• Combining different versions together

36. Git Commands
Version Control Is:
• Making changes while retaining a master copy
• git clone OR git branch
• Having multiple copies of the same file/project
• git branch
• Saving changes
• Undoing Changes
• Combining different versions together

37. Git Commands
Version Control Is:
• Making changes while retaining a master copy
• git clone OR git branch
• Having multiple copies of the same file/project
• git branch
• Saving changes
• git add; git commit; git push
• Undoing Changes
• Combining different versions together

38. Git Commands
Version Control Is:
• Making changes while retaining a master copy
• git clone OR git branch
• Having multiple copies of the same file/project
• git branch
• Saving changes
• git add; git commit OR git branch
• Undoing Changes
• git reset OR git revert
• Combining different versions together

39. Git Commands
Version Control Is:
• Making changes while retaining a master copy
• git clone OR git branch
• Having multiple copies of the same file/project
• git branch
• Saving changes
• git add; git commit OR git branch
• Undoing Changes
• git reset OR git revert
• Combining different versions together
• git merge OR git rebase

40. Have A Copy on a Server

41. Copy To Desktop

42. git clone

43. Save With a New Name

44. git branch InfoLitED110

45. Make Some Changes and Save

46. git add InfoLit.ppt

47. git commit -m ‘Change
Presentation Title’

48. git push

49. git push (if remote)

50. Or Close Without Saving

51. git reset InfoLit.ppt

52. Occasionally We Update
The Final Presentation

53. So We Review Changes

54. git merge

55. Scary!

56. Scary!

57. Even More Scary!

58. Pick The Updates We Like

59. Not So Scary!

60. Until Everyone is Synched Up

61. Repeat

62. #Winning