GitHub Basics: The Developer Playground 🐙

I recently completed the GitHub Skills exercise Introduction to GitHub, and honestly… it felt like unlocking the starter pack of the developer universe.

If you’re new to coding, GitHub can look intimidating at first branches, commits, pull requests… sounds like a forest of technical jargon 🌲.

But once you understand the basics, it’s actually pretty fun.

So here’s a quick and quirky guide to GitHub basics based on what I learned.

1. What is GitHub?

Think of GitHub as:

Google Drive + version history + collaboration for developers.

It’s where developers store projects, track changes, and work together without overwriting each other’s code.

It runs on top of Git, which is the engine that tracks every change you make.

Imagine writing a book where every draft is saved forever and you can go back anytime. That’s basically Git.

2. Repository (Repo) 🗂️

A repository is simply your project folder on GitHub.

It contains:

• code
• images
• documentation
• configuration files
• basically anything related to your project

Example:

moneyhub/
   app.js
   styles.css
   README.md

Every project on GitHub lives inside a repository.

3. Branch 🌿

A branch is like creating a parallel universe of your project.

Your main project usually lives in a branch called: main

But suppose you want to try something new.

Instead of breaking the main project, you create another branch:

my-first-branch

Now you can experiment freely without messing up the original project.

Think of branches like save files in a video game 🎮.

4. Commit

A commit is a snapshot of your changes.

Whenever you update something, you “commit” it with a message explaining what changed.

Example commit message:

Add PROFILE.md
Fix login bug
Update UI colors

A good commit message is like leaving notes for your future self.

5. Push

When you commit locally, the change lives on your computer.

Get Tanisha fonseca’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

To send it to GitHub, you push it.

git push

Think of pushing as uploading your progress to the cloud.

6. Pull Request (PR)

This is where collaboration happens.

A pull request means:

“Hey everyone, I made some changes. Can we add them to the main project?”

Other developers can:

• review the code
• suggest improvements
• approve or reject changes

It’s basically a discussion thread for code.

7. Merge 🔀

Once everyone agrees that your changes look good, the pull request gets merged.

That means your branch’s changes are officially added to the main branch.

Your experiment becomes part of the real project .

What I Actually Did in the Exercise

During the exercise I:

1️⃣ Created a branch
2️⃣ Added a file (PROFILE.md)
3️⃣ Made my first commit
4️⃣ Opened a pull request
5️⃣ Merged it into main

And just like that…

I made my GitHub contribution.

Why GitHub Is Powerful

GitHub makes it possible for thousands of developers to collaborate on the same project without chaos.

Huge projects like Linux and React are built this way.

Developers from all over the world contribute through branches, commits, and pull requests.

Pretty amazing when you think about it.

Final Thoughts

Learning GitHub is like learning the grammar of coding collaboration.

Once you know:

• repositories
• branches
• commits
• pull requests

you can contribute to projects anywhere in the world.

And honestly, seeing that first merged pull request feels like leveling up in a game .

If you’re new to GitHub too, I highly recommend trying the GitHub Skills exercises.

They’re interactive, beginner-friendly, and surprisingly fun.

Happy coding!