Let's try using "GitHub" | It's surprisingly simple if you think of it as game "save data"🎮

Good evening, this is Kyon✨

With terms like "vibe coding" starting to trend, I'd love to try programming with AI.

But while thinking that, didn't you feel a little intimidated when you encountered these terms along the way?🤭

"Push to GitHub"
"Create a branch"
"Submit a pull request"

...It feels like, what on earth does that mean?💦

I was the same way at first😇

Even though AI helped me get a feel for programming, these terms suddenly started looking like jargon.

But when I actually tried using it, it was actually a concept close to games after all😇
I'd be happy if we could look at it together while organizing things a bit🌸

First, what is the difference between "Git" and "GitHub"?

I think this is where it's easy to get confused💦

Git is the mechanism itself that records file change history.
GitHub is a place where you can save and share those records on the internet.

In terms of games, it might be something like this.

Git = The save function itself
GitHub = Cloud storage that manages save data online

Because there is a save function (Git), you can take records, and because there is a cloud (GitHub), you can call them up from anywhere.

I think that's the kind of relationship it is✨

Translating jargon into game terms

This might be the part that feels like the biggest hurdle💦

I'll try replacing them one by one with game imagery.

🌿 Branch — "Save slot for retries"

In a game, when you want to "keep the main data but try proceeding on a different route," you save to a separate slot, right?

Branchesare based on that same concept.

It is a feature that creates a separate data line for "trying out new features without touching the main work."

Even if you fail, the main data remains intact.
It's like a place where you can experiment with peace of mind🥰

This is how it looks in the Claude Code chat box✨

💾 Commit — "Save"

After clearing an important event in a game, you sometimes manually save by saying, "I'll save here," right?🤭

Commitis exactly that feeling.

It is an operation where you save your changes with a note at the point when you feel, "This task is finished, so I'll leave a record."

For example, you record what you did with a short note, like "Changed the title screen design" or "Fixed a bug"✨

This note is called a "commit message," and in terms of a game, it might be like the "play time" or "current location" attached to save data🥰

The important thing is thatsaving frequently gives you peace of mind.

Even in games, you've had the experience of despairing when the game freezes after playing for a long time without saving... right?💦

Commits are the same; if you record frequently at good stopping points in your work, it becomes easier to go back if something happens🌸

📤 Push — "Upload save data to the cloud"

When you perform a "cloud save" in a game, you send your local data online, right?

Pushis exactly that operation.

You upload the record of the work you did on your computer to GitHub.

"Saved locally → Reflect it on GitHub as well"
That is the image of how you use this flow✨

🔀 Pull Request — "Do you want to overwrite the main story with this route's data?"

Can you imagine a situation where you've tried a route in a separate slot and think, "I want to put this into the main story!", so you ask, "Are you sure you want to overwrite the save data?"

Pull Request (PR) is that process.

It's a feature on GitHub for proposing, "Please check if it's okay to incorporate the changes from this branch (separate slot) into the main one."

It's especially important when working in a team, and it's designed so you can see at a glance "who changed what and when"😇

🔗 Merge — "Overwrite save the sub-data into the main data"

Once the pull request gets the OK, the next step is finally integration.

Merge is the operation of incorporating changes made in a separate branch into the main data.

In game terms, it's like "reflecting sub-event data into the main story."

With this, the main data is updated to the latest state🌸

If you connect the whole flow, it looks like this

To organize it a bit, the flow looks like this.

1. Create a branch → Prepare a separate slot for testing
2. Commit → Save
3. Push → Upload to the cloud
4. Issue a pull request → Ask "Can I incorporate this into the main story?"
5. Merge → Integrate into the main story data

I think the basic way to use it is to repeat this process while building up your work little by little💕

At first, you should just use it as a "single-player game"

Some people might think, "Isn't Git something you use in a team?", but I feel it's best to start using it alone at first✨

I use it alone for personal development, after all🤭

Push → Changes are recorded → You can redo it even if you fail.

I feel that just gaining this experience is reason enough to use GitHub😇

You don't need to overthink it.

I hope you'll start slowly by using it as a "workspace that can auto-save"🌸

If there's anything you still don't understand or any terms you're curious about, I'll write another article about them.

Let's get used to it little by little together✨

#GitHub #ProgrammingBeginner #Engineer #Git #VibeCoding

📱SNS

I'm also on social media, so please follow me!

🔵X

⚫Threads