Intro to Git, GitHub, and Devpost
3 likes673 views
The document provides an overview of Git, GitHub, and Devpost for code collaboration. It introduces version control with Git and how it allows developers to work together through features like branching and merging. GitHub is presented as a way to host Git repositories and provide additional collaboration tools. The document walks through setting up a GitHub repository and preparing it for submission to Devpost for a hackathon.
![can also use git add [filename]
for individual files
Git, GitHub, and Devpost 33](https://image.slidesharecdn.com/presentation-160123070443/85/Intro-to-Git-GitHub-and-Devpost-33-320.jpg)
![git branch [branchname]
Git, GitHub, and Devpost 41](https://image.slidesharecdn.com/presentation-160123070443/85/Intro-to-Git-GitHub-and-Devpost-41-320.jpg)
![git merge [branchname]
Git, GitHub, and Devpost 45](https://image.slidesharecdn.com/presentation-160123070443/85/Intro-to-Git-GitHub-and-Devpost-45-320.jpg)
![git remote add origin [url]
Git, GitHub, and Devpost 58](https://image.slidesharecdn.com/presentation-160123070443/85/Intro-to-Git-GitHub-and-Devpost-58-320.jpg)
Intro to Git, GitHub, and Devpost
- 1. Code Collaboration and Submission Git, GitHub, and Devpost 1
- 2. Git, GitHub, and Devpost Git, GitHub, and Devpost 2
- 3. whoami Git, GitHub, and Devpost 3
- 4. whoami • Fifth year Software Engineering @ UF Git, GitHub, and Devpost 4
- 5. whoami • Fifth year Software Engineering @ UF • Officer of the UF Student InfoSec Team Git, GitHub, and Devpost 5
- 6. whoami • Fifth year Software Engineering @ UF • Officer of the UF Student InfoSec Team • Full stack web developer Git, GitHub, and Devpost 6
- 7. whoami • Fifth year Software Engineering @ UF • Officer of the UF Student InfoSec Team • Full stack web developer • Currently web eng lead at Quottly Git, GitHub, and Devpost 7
- 8. whoami • Fifth year Software Engineering @ UF • Officer of the UF Student InfoSec Team • Full stack web developer • Currently web eng lead at Quottly • Former security intern at Tumblr Git, GitHub, and Devpost 8
- 9. whoami • Fifth year Software Engineering @ UF • Officer of the UF Student InfoSec Team • Full stack web developer • Currently web eng lead at Quottly • Former security intern at Tumblr • Former intern at BlockScore Git, GitHub, and Devpost 9
- 10. whoami • Fifth year Software Engineering @ UF • Officer of the UF Student InfoSec Team • Full stack web developer • Currently web eng lead at Quottly • Former security intern at Tumblr • Former intern at BlockScore • Reach me @andrew on Slack Git, GitHub, and Devpost 10
- 11. Git Git, GitHub, and Devpost 11
- 12. At it's core, git is version control Git, GitHub, and Devpost 12
- 13. What is version control? Git, GitHub, and Devpost 13
- 14. Version control tracks changes in your code Git, GitHub, and Devpost 14
- 15. Git, GitHub, and Devpost 15
- 16. Why is this useful? Git, GitHub, and Devpost 16
- 17. Collaboration Git, GitHub, and Devpost 17
- 18. How does this work? Git, GitHub, and Devpost 18
- 19. How does this work? 1. Download code from remote server Git, GitHub, and Devpost 19
- 20. How does this work? 1. Download code from remote server 2. Make your changes Git, GitHub, and Devpost 20
- 21. How does this work? 1. Download code from remote server 2. Make your changes 3. Upload code to remote server Git, GitHub, and Devpost 21
- 22. How does this work? 1. Download code from remote server 2. Make your changes 3. Upload code to remote server 4. Version control figures out what has changed and applies those changes to the codebase Git, GitHub, and Devpost 22
- 23. Cool, so let's talk about git Git, GitHub, and Devpost 23
- 24. Git Basics Git, GitHub, and Devpost 24
- 25. Open up a terminal! Git, GitHub, and Devpost 25
- 26. 1. Make a new directory Git, GitHub, and Devpost 26
- 27. 2. git init Git, GitHub, and Devpost 27
- 28. 3. git status Git, GitHub, and Devpost 28
- 29. 4. Make a file Git, GitHub, and Devpost 29
- 30. 5. git status Git, GitHub, and Devpost 30
- 31. 6. git add . Git, GitHub, and Devpost 31
- 32. 6. git add . • "staged files" are files that are ready to be committed to git • "unstaged files" are files that have changes that have not been prepared to be committed Git, GitHub, and Devpost 32
- 33. can also use git add [filename] for individual files Git, GitHub, and Devpost 33
- 34. 7. git status Git, GitHub, and Devpost 34
- 35. 8. git commit -m 'Summary of changes' Git, GitHub, and Devpost 35
- 36. 9. git log Git, GitHub, and Devpost 36
- 37. Any questions? Git, GitHub, and Devpost 37
- 38. Git Branches Git, GitHub, and Devpost 38
- 39. Git Branches • A "copy" of code that developers can work on independently of the main code base Git, GitHub, and Devpost 39
- 40. Git Branches • A "copy" of code that developers can work on independently of the main code base • The main code base is normally "master" • Once the developer is done, can "merge" it back into master Git, GitHub, and Devpost 40
- 41. git branch [branchname] Git, GitHub, and Devpost 41
- 42. Once we have a new branch, we follow the git flow Git, GitHub, and Devpost 42
- 43. We have new code on a branch, how do we merge back? Git, GitHub, and Devpost 43
- 44. git checkout master Git, GitHub, and Devpost 44
- 45. git merge [branchname] Git, GitHub, and Devpost 45
- 46. Using branches allows for multiple developers to work on the same code base Git, GitHub, and Devpost 46
- 47. Any questions? Git, GitHub, and Devpost 47
- 48. Git Remotes Git, GitHub, and Devpost 48
- 49. Git Remotes • A remote server for your git repository! Git, GitHub, and Devpost 49
- 50. Git Remotes • A remote server for your git repository! • This is where GitHub comes in... Git, GitHub, and Devpost 50
- 51. GitHub Git, GitHub, and Devpost 51
- 52. Powerful collaboration, code review, and code management for open source and private projects. Git, GitHub, and Devpost 52
- 53. Helps put a GUI on top of git! Git, GitHub, and Devpost 53
- 54. Sign up for GitHub at github.com Git, GitHub, and Devpost 54
- 55. Once signed up, create a repository Git, GitHub, and Devpost 55
- 56. Get the remote ssh url Git, GitHub, and Devpost 56
- 57. Back to the command line... Git, GitHub, and Devpost 57
- 58. git remote add origin [url] Git, GitHub, and Devpost 58
- 59. git remote -v Git, GitHub, and Devpost 59
- 60. So, how do we get code on our remote? Git, GitHub, and Devpost 60
- 61. git push Git, GitHub, and Devpost 61
- 62. Awesome! Now we've got code on GitHub Git, GitHub, and Devpost 62
- 63. Once a teammate pushes changes, make sure to use git pull to download the new changes Git, GitHub, and Devpost 63
- 64. Any questions? Git, GitHub, and Devpost 64
- 65. GitHub + Devpost Git, GitHub, and Devpost 65
- 66. Git, GitHub, and Devpost 66
- 67. Preparing your GitHub repo for submission Git, GitHub, and Devpost 67
- 68. 1. Create a README.md file Git, GitHub, and Devpost 68
- 69. Example: https://github.com/ andrewjkerr/hackathon-mentor- request-slackbot Git, GitHub, and Devpost 69
- 70. Git, GitHub, and Devpost 70
- 71. 2. Set the description Git, GitHub, and Devpost 71
- 72. "A slackbot to help manage mentorship requests for hackathons (aka SwampHacks)." Git, GitHub, and Devpost 72
- 73. Anddd that's it! Pretty easy, eh? Git, GitHub, and Devpost 73
- 74. To review Git, GitHub, and Devpost 74
- 75. To review 1. git pull Git, GitHub, and Devpost 75
- 76. To review 1. git pull 2. git checkout -b branch Git, GitHub, and Devpost 76
- 77. To review 1. git pull 2. git checkout -b branch 3. Make changes Git, GitHub, and Devpost 77
- 78. To review 1. git pull 2. git checkout -b branch 3. Make changes 4. git add . Git, GitHub, and Devpost 78
- 79. To review 1. git pull 2. git checkout -b branch 3. Make changes 4. git add . 5. git commit -m 'commit summary' Git, GitHub, and Devpost 79
- 80. To review 1. git pull 2. git checkout -b branch 3. Make changes 4. git add . 5. git commit -m 'commit summary' 6. git checkout master Git, GitHub, and Devpost 80
- 81. To review (continued...) 1. git pull Git, GitHub, and Devpost 81
- 82. To review (continued...) 1. git pull 2. git merge branch Git, GitHub, and Devpost 82
- 83. To review (continued...) 1. git pull 2. git merge branch 3. git push Git, GitHub, and Devpost 83
- 84. To review (continued...) 1. git pull 2. git merge branch 3. git push 4. Do it all again! Git, GitHub, and Devpost 84
- 85. Git and GitHub can help teams work more efficiently on code Git, GitHub, and Devpost 85
- 86. (And it doesn't hurt that GitHub works well with Devpost) Git, GitHub, and Devpost 86
- 87. Any questions? Git, GitHub, and Devpost 87
- 88. Slides available at talk.andrewjkerr.com Git, GitHub, and Devpost 88