Git + Github introduction

An introduction to git and github for Napier's Developers Society.

Transcript

1. git:hub how to
2. how to use git github
3. github SOCIAL CODING
4. we work asynchronously
5. Working asynchronously: You can do shit without needing to pull me out of the zone™.
6. okay let’s talk about: CREATING AN ACCOUNT MAKING REPOSITORIES PULL REQUESTS + BRANCHING ISSUES
7. AN account creating
8. Who hasn’t done this yet?
9. DO IT NOW!
10. Y’all got some weird branches.
12. Keep you branches simple.
13. develop master initial working commit finished super ninja feature add cats feature work on latest feature
14. Everyone can push.
15. Master is always deployable.
16. Keep you branches simple.
17. Supporting branches: HOTFIXES FEATURES RELEASES
18. develop master FEATURE
19. git merge --no-ff <branch>
20. it shows feature implementation, makes reverts easier.
21. Keep you branches simple.
22. What about code quality? ಠ_ಠ
23. REQUESTS PULL OOH! SCIENTIFIC!
24. Pull requests are code review.
25. PULL REQUESTS? WHAT ARE DISCUSSIONS DISCUSSIONS ONS DISCUSSIONS DIS DISCUSSIONS DISCUSSIONS ONS DISCUSSIONS DIS DISCUSSIONS DISCUSSIONS ONS DISCUSSIONS DIS DISCUSSIONS DISCUSSIONS ONS DISCUSSIONS DIS DISCUSSIONS DISCUSSIONS ONS DISCUSSIONS DIS DISCUSSIONS DISCUSSIONS ONS DISCUSSIONS DIS DISCUSSIONS DISCUSSIONS ONS DISCUSSIONS DIS DISCUSSIONS DISCUSSIONS ONS DISCUSSIONS DIS DISCUSSIONS DISCUSSIONS ONS DISCUSSIONS DIS DISCUSSIONS DISCUSSIONS ONS DISCUSSIONS DIS DISCUSSIONS DISCUSSIONS ONS DISCUSSIONS DIS DISCUSSIONS DISCUSSIONS ONS DISCUSSIONS DIS
26. A PULL REQUST IS A DISCUSSION CODE DISCUSSION FEATURE DISCUSSION STRATEGY DISCUSSION
27. CODE DISCUSSION FEATURE DISCUSSION STRATEGY DISCUSSION
28. CODE DISCUSSION FEATURE DISCUSSION STRATEGY DISCUSSION REFERENCE ISSUES WRITE CODE COMMENTS REVIEW CODE DIFFS
30. TITLE OF PULL REQUEST D E S C R I P T I O N COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT DISCUSS DISCUSS DISCUSS DISCUSS DISCUSS DISCUSS DISCUSS DISCUSS DISCUSS COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT COMMIT
31. use issues
32. Types of useful issues. 3
33. Shit, something is broken
34. Wouldn’t this be awesome?
35. todo lists
36. SIMPLE TOOLS YOUR PROJECT MEANS MORE TIME CODING
37. secrets github has
38. EMOJI WORDS ARE BORING, BRO :heart: :+1: :shipit: ...and so much more: http://git.io/dmWZWg
39. SHORTCUTS 3\/3RY0N3 L0\/35 L337 w t ? ...and so much more: http://git.io/dmWZWg
40. so what is git ?
41. AWESOME
42. Snapshots, not differences.
43. Checkins over time Version 1 Version 2 Version 3 Version 4 A B C A1 A1 A2 B B B1 C C1 C2
44. 3 step program working directory staging area git directory (repository) checkout the project stage files commit
45. Commands, will do. 4For most of the time.
46. git clone <url> git add <file> git commit -m “<Brilliant comment>” git push
47. one more thing
48. HOMEWORK TIME SUPER! FANTASTIC! FOR
49. Minutes, that’s all. 15
50. http://try.github.com/levels/1/challenges/1
51. Questions?