Git and Github: version control for the 21st century

Transcript

1. PyLadies Montréal :: October 22, 2013 version control for the

   21st century and :

2. about me - Wendy Liu - Math & CS at

   McGill - 2.5 years experience with Git

3. what is git?

4. what is git? version control system!

5. svn/perforce: local vs. remote comparison to other systems

6. svn/perforce: local vs. remote hg/bzr: faster, more control comparison to

   other systems

7. svn/perforce: local vs. remote hg/bzr: faster, more control cvs/rcs: no

   comparison comparison to other systems

8. backup_dec_1_2012.zip backup_dec_8_2012.zip backup_dec_15_2012.zip backup_dec_22_2012.zip backup_dec_29_2012.zip backup_jan_5_2012.zip backup_jan_12_2012.zip backup_jan_19_2012.zip backup_jan_26_2012.zip

9. report_v1.doc report_v2.doc report_v3.doc report_v4.doc

10. keeps track of changes enter git.

11. keeps track of changes extremely flexible enter git.

12. keeps track of changes extremely flexible developed by linus torvalds

    enter git.

13. keeps track of changes extremely flexible developed by linus torvalds

    completely free to use (and open source!) enter git.

14. keeps track of changes extremely flexible developed by linus torvalds

    completely free to use (and open source!) primarily command-line enter git.

15. website what is github?

16. website collaborative coding, via git what is github?

17. website collaborative coding, via git (mostly) free to use what

    is github?

18. website collaborative coding, via git (mostly) free to use major

    part of developer ecosystem (esp. OSS) what is github?

19. why git?

20. why git? diffs

21. why git? diffs backups

22. why git? diffs backups collaboration

23. what git can do for you versioning easy collaboration blame

    tracking down bugs safe experimentation statistics

24. what github can do for you issue-tracking even easier collaboration

    remote backups access your files from anywhere graphical, easy-to-use UI

25. now: how git works

26. repository directory on filesystem just metadata (changes) manual grouping of

    changes

27. commit group of logically-related changes 1 or more files (add/delete/modify)

28. staging index CHANGES I WANT IN MY NEXT COMMIT ALL

    THE OTHER CHANGES

29. git commit -m 'test' CHANGES I WANT IN MY NEXT

    COMMIT ALL THE OTHER CHANGES a new commit, with message 'test'

30. CHANGES I WANT IN MY NEXT COMMIT ALL THE OTHER

    CHANGES the commit with message 'test' (nothing here yet)

31. git demo

32. github demo

33. further resources help.github.com gitimmersion.com git-scm.com/book try.github.com git man pages (git

    help, git help [command]) github.com/Gazler/githug

34. thanks! @dellsystem