The document discusses Git, an open source distributed version control system originally designed and developed by Linus Torvalds. It provides information on why Git is useful for group work, allowing developers to work offline and easily branch and merge files. The document then demonstrates how Git works with developers committing changes to local repositories and pushing them to a shared central repository. It provides guidance on setting up Git with GitHub and gives an overview of common Git commands.

1. Sten Govaerts
KU Leuven

2. what the hell...
• distributed version control

3. what the hell...
• distributed version control
• originally designed and developed by Linus
Thorvalds.

4. what the hell...
• distributed version control
• originally designed and developed by Linus
Thorvalds.
• git (plural gits) (noun)
• (UK, slang, pejorative) A contemptible person.
• (UK, slang, pejorative) A silly, incompetent,
stupid, annoying or childish person.

5. distributed?
centralised distributed
version control version control
GIT
SVN or CVS
http://www.slideshare.net/lydian/git-tutorial

6. but why?...
• easier offline usage

7. but why?...
• easier offline usage
• easier to branch projects

8. but why?...
• easier offline usage
• easier to branch projects
• git is good at merging files and re-joining
branches

9. git philosophy
• Commit early, commit often!
• 1 commit = 1 idea or change
• easy to read patches by team members
• easy to revert changes later
• local repo is your working directory

10. why do we need this?
• group work
• help each other
• work on multiple locations
• common back-end development?
• learning analytics

11. how does it work?
file states
• modified
• staged
• commited

12. how does it work?

13. how does it work?
dev B
shared
repo
dev A dev C

14. how does it work?
dev B
git clone
shared
repo
dev A dev C

15. how does it work?
dev B
shared
git push repo
dev A dev C

16. how does it work?
dev B
shared
git push repo
dev A dev C

17. how does it work?
dev B
shared
git push repo git push
dev A dev C

18. how does it work?
dev B
shared
git push repo git push
dev A dev C

19. how does it work?
dev B
shared
git push repo
dev A dev C

20. how does it work?
dev B
shared git fetch
git push repo
git merge
dev A dev C

21. • http://www.github.com
• make an account (use twitter name) and
one repository per group
• put repository link on wiki
• http://ariadne.cs.kuleuven.be/wiki

22. what do you do next?
• student A makes the github repository

23. what do you do next?
• student A makes the github repository
• student A commits his work to his local
repository and pushes to github

24. what do you do next?
• student A makes the github repository
• student A commits his work to his local
repository and pushes to github
• student B fetches the repository, commits
his work locally and pushes to github

25. what do you do next?
• student A makes the github repository
• student A commits his work to his local
repository and pushes to github
• student B fetches the repository, commits
his work locally and pushes to github
• student C fetches the repository, commits
his work locally and pushes to github

26. how to do this?
• command line (4 1337 h4x0rz)
• IDE tools
• eclipse (http://www.vogella.com/articles/EGit/article.html)
• xcode (http://support.beanstalkapp.com/customer/portal/
articles/95580-setting-up-git-with-xcode-4 & http://
developer.apple.com/library/mac/#recipes/xcode_help-
repositories_organizer/articles/
CommittingFilestoaRepository.html#//apple_ref/doc/uid/
TP40010350-CH8-SW1)

27. tools
• http://eclipse.github.com/
• http://windows.github.com/
• http://mac.github.com/

28. git commands cheat
sheet
• http://www.git-tower.com/files/cheatsheet/
Git_Cheat_Sheet_grey.pdf

29. further reading...
• Setup github
• Create a repo on github
• Fork a repo
• Everyday GIT with 20 commands or so
• Advanced GIT tutorial
• GITcasts
• Git docs