Enjoy a technical overview of working with a GIT repository, its advantages and benefits, and how to set it up.

1. Welcome to: GIT … and Drupal sitting in a Tree ( yes – the data-structure ) A DrupalCape Presentation by: Perceptum Thought Squad 20/Apr/2011 Presenter: Bryan Gruneberg

4. Branching

5. Merging

7. What Perceptum Does

8. Why CI makes sense 20/Apr/2011 Presenter: Bryan Gruneberg

10. http://vimeo.com/20459209 - Using Git on Drupal.org 20/Apr/2011 Presenter: Bryan Gruneberg

12. Take CVS as an example of what not to do; if in doubt, make the exact opposite decision

13. Support Distributed Version Control

14. Strong safeguards against corruption

15. HIGH PERFORMACE

16. Design is a synthesis of Linus' experiences in maintaining a large distributed development project 20/Apr/2011 Presenter: Bryan Gruneberg

19. Stupid. Contemptible and despicable. Simple. Take your pick from the dictionary of slang.

20. "Global information tracker": you're in a good mood, and it actually works for you. Angels sing and light suddenly fills the room.

21. "Goddamn idiotic truckload of sh*t": when it breaks 20/Apr/2011 Presenter: Bryan Gruneberg

23. Distributed development

24. Compatibility with existing systems/protocols (HTTP, FTP, RSYNC, SSH)

25. Efficient large projects (does not get slower as the project history grows)

27. Pluggable merge strategies (attempted merge 1,2...,n => error)

29. Packing similar files together

30. Periodic packing done by GIT... or “git gc –prune” to force 20/Apr/2011 Presenter: Bryan Gruneberg

32. The other half does go through all the concepts, but they explain Git in a manner that assumes you already understand how Git works

33. Merely memorizing which commands you should run at what times will work in the short run (SO DO IT!!!)

34. But it’s only a matter of time before you get stuck or break something... so here is an overview of what happens inside the big-black-git-box... 20/Apr/2011 Presenter: Bryan Gruneberg

36. References to parent commit objects.

38. Graphically... 20/Apr/2011 Presenter: Bryan Gruneberg

41. a timestamp,

42. a log message, and

45. A project always has one commit object with no parents. This is the first commit made to the project repository (initial commit)

50. A repository can contain any number of heads

52. “ HEAD” (uppercase) refers exclusively to the currently active head

53. This is used seen in Git documentation, and isn't always explicitly explained 20/Apr/2011 Presenter: Bryan Gruneberg

54. Looks like this... 20/Apr/2011 Presenter: Bryan Gruneberg

56. You commit the theme code, and let customers review

57. While they review, you carry on with new functionality

58. They revert and ask that all <span class=header> tags to be changed to <h4> tags

59. You want to fix the code for them, but you don't want them to have access to the half-baked new feature code 20/Apr/2011 Presenter: Bryan Gruneberg

60. Branching... 20/Apr/2011 Presenter: Bryan Gruneberg

61. Branching... result 20/Apr/2011 Presenter: Bryan Gruneberg

63. Git merge 20/Apr/2011 Presenter: Bryan Gruneberg

65. Git pull

71. Drupal now uses GIT (yay)

72. Drupal.org account integrated with git account

73. Drupal.org projects are all git repositories

74. Drupal core is in GIT 20/Apr/2011 Presenter: Bryan Gruneberg

76. Only share .pub!!!

78. Contribute to modules where you have been given access 20/Apr/2011 Presenter: Bryan Gruneberg

79. What Perceptum does... 20/Apr/2011 Presenter: Bryan Gruneberg

80. Why CI Makes Sense 20/Apr/2011 Presenter: Bryan Gruneberg