That’s the first thought that came to my mind after being asked to create my own repository on GitHub and connect it to my own local repo.
Surprisingly enough, I had ran across GitHub a few years prior when I was researching coding. A few minutes after creating an account, I felt this platform was way over my head. I didn’t understand its purpose. How was this supposed to help me become a coder? It was foreign and intimidating. Instead of attacking GitHub head on, I’d simply avoided it (kind of like that trip to the gym I planned last week). Well, so much for that idea. Here was GitHub all these years later. Back with a vengeance.
What is GitHub you ask? Ugghhhh….
Here’s the formal definition from Wikipedia in case you want it:
“GitHub Inc. is a web-based hosting service for version control using Git. It is mostly used for computer code. It offers all of the distributed version control and source code management functionality of Git as well as adding its own features.” — GitHub. Wikipedia, The Free Encyclopedia.
I’m starting my coding journey right now (which I literally am by the way. 1 month in… Yay me!) on my own computer. As I’m working on an exercise or project, however, I want others to be able to see my work. Just to show off. Collaborate with a peer. Maybe for potential employers to see. To contribute to the stockpile of code out there. I will push my code to GitHub.
With anything, the first version is never your best. The second, third, or fourth may not be the finished product either. This is where GitHub becomes handy. It not only stores my code, but keeps a log of all the versions of my project. Someone can come along and see my work. Download it for themselves and work on it too. Upload their changes. It’s a great tool for collaboration. You don’t have to be a developer to use it.
Last thing I want to say are the 3 lines you’ll write in your terminal all the time when moving your code from your local repo to the GitHub repository.
- Git add .
- Git commit -m “your commit statement”
- Git push
The first command is to add your files to the staging area. The second command will take everything you’ve staged and place it into your local repository. Your commit statement explains the changes you’ve made. The last command will move your code from your local repository to a remote repository like Github. In the words of Salt N Pepa