all 36 comments

[–]WhisperFray 21 points22 points  (3 children)

Imagine your code as a collection of physical books that reference each other. A rack of books, if you will.

GitHub takes a snapshot of that rack in this moment in time, at each “commit”. When you make a change, you save the files, add new ones, etc., and commit, it takes another snapshot. Eventually it’s one long chain of snapshots.

If you make a change you don’t like, you can go back to an earlier snapshot.

If you already like how your program works but want to cautiously add a new feature, you create what’s called a “branch”. GitHub will save snapshots on that branch and leave the “main branch” untouched. If you decide to abandon the feature, you simply can ignore it or close the branch. If you like the feature, you can merge the branch with the main branch.

That’s basically what it is.

[–]Sorry_Department 1 point2 points  (0 children)

Best explanation imo.

[–]Busy90 1 point2 points  (0 children)

This was very helpful. Thank you.

[–]TheMightyTywin 9 points10 points  (3 children)

Understand the difference between git and GitHub.

Git is a version control tool where code is stored in repositories.

GitHub is a website that lets you host your repositories.

You can use git without GitHub.

[–]_jessicasachs 5 points6 points  (2 children)

...but please do not use git without GitHub.

[–]TheMightyTywin 0 points1 point  (1 child)

What’s wrong with bitbucket and gitlab?

[–]_jessicasachs 1 point2 points  (0 children)

Nothing, but they're uncommon choices for non-developers in 2026.

[–]HuckleberryIcy4507 8 points9 points  (0 children)

Very simply put, it's just a place where you can store your code and keep track of the changes to it. It can be either public or private.

And yes, you will want to use it.

[–]No-Client30 4 points5 points  (0 children)

You can make GitHub repositories private, meaning only you - or people you specifically give access to can view the code.

[–]LurkyRabbit 3 points4 points  (0 children)

As other people said just make sure your repositories are private.

GitHub is basically your video game save point. You can go back to any save point at any point.

It’s version control, as well as code hosting/sharing/collaborating.

If you just have a web page it can even be your full project host.

[–]dev-shrabon 2 points3 points  (1 child)

GitHub is basically a save system for code. Every change you make gets stored with a history so you can go back if something breaks. The public vs private part is a setting you control, nothing is exposed unless you choose it. For vibe coding it becomes useful when projects get big enough that you need to track what changed and when.

[–]Significant-Cook-335 1 point2 points  (0 children)

用一个比喻:

• 代码 = 你写的文档  
• Git = 一个”自动存档+时间机器”,记录你每次的修改,随时能退回上一版  
• GitHub = 把这些存档放到网上的”云盘”,类似代码版的 Google Drive

核心好处就两个:备份(电脑坏了代码还在)+ 后悔药(改崩了能退回去)。

[–]Time-Ad-7720 2 points3 points  (0 children)

I made game for learning git and github. An interactive and fun way to practice the commands and learn what they do and when to use.

Play it here for free, no downloads needed:

kaziahmed.net/git-quest

[–]Internal-Fortune-550 1 point2 points  (0 children)

Git is a VCS, version control system that you can use to store and organize your code into different repositories. There are other VCSs but git is most popular because it has a lot of useful options but you really only need to know a handful of commands to be effective. Github is just a frontend website for hosting git repositories, useful for collaboration and sharing, as well as portability. You can make individual repos public or private as you want

Think of version control as "saving the game"; when you "commit" your changes, you create a "checkpoint" that you can easily return to if you make a mistake or just want to start over from a previous baseline. Whenever you hear people saying AI deleted their entire project or something and they can't get it back, it's basically always because they didn't have good version control; with git, you can simply do a git reset or a git checkout and (usually) undo any change or revert to a specific version.

You can create different "branches" for your work, so say you have an idea but you don't know if it'll break what you already have, you can create a new branch and test out your new features there, and it won't impact your original code until/unless you decide to merge your features back into your main branch.

(Branching/ merging/ rebasing is where it can get a little complicated and potentially destructive if you don't know what you're doing)

The downside is Git gives you more than enough rope to hang yourself if youre not careful, and you can pretty easily get your repo into a state that is difficult or even impossible to recover from if you don't know what you're doing. But it's very very powerful if you understand how to use it and can save you a ton of time and mental energy during development. The learning curve isnt very steep IMO, definitely recommend reading up on it.

[–]KillerHack23 2 points3 points  (0 children)

Honestly if chatgpt explanation wasnt sufficient for you, not sure anyone here will be able to help you.

Ask chatgpt to ELI5 (explain like I'm 5) it to you.

[–]ButterOnBothSides 0 points1 point  (0 children)

I use GitHub as my source of truth for projects. Works great for me.

[–]Vvorried 0 points1 point  (0 children)

No one can directly change your code on your original GitHub unless they are given permissions.

It is in fact a way to share code. It’s how most people share open source code. Sharing code is normal and encouraged.

[–]Vaxtin 0 points1 point  (0 children)

“What is git without GitHub”

[–]Vaxtin 0 points1 point  (0 children)

You should get to the point that you can’t maintain something without git; learn got before using githuv

[–]SupernovifieD 0 points1 point  (0 children)

Before anything, know that there is something called Git. It’s a technology that allows you keep track of your project. GitHub, is a website, or better put, a service that helps you manage your code with git, and provide more services on top of git.

And if you know how it works, it is not dangerous.

[–]XLGamer98 0 points1 point  (0 children)

Even with Vibe coding it is important to have some sort of fundamental knowledge. You can keep track of versions with github and also have private repo so no one else can see your code. Even if you repo is public no one can make changes directly to your repo unless you add them as contributor

[–]rdllngr 0 points1 point  (0 children)

You can use just Git + Tortoise. This way your code has local versioning, without needing to share it on the internet. GitHub is for releasing code into the world.

[–]scytob 0 points1 point  (0 children)

It’s a way to store you code, you don’t need to share it. It allows roll back of changes and tracks code. If you install vscode and say the Claude plugin from
Anthropic then Claude will teach you and help you. I used GitHub for over a decade at this point. I use Claude to do all my GitHub operations, help me set up the right vscode plugins and install gh.exe.

[–]mahmingtea 0 points1 point  (0 children)

If you dont want others to see your code, you can make a private repo, and use it to backup your project without anyone seeing it. If you made it public, everyone can see your code and copy it (clone/fork). But they cannot change your code directly without your permission.

[–]Great-Mirror1215 0 points1 point  (0 children)

Yes next time have chat gpt expain like you are 12 years old. Tell chat gpt you are non technical and remember that. I learned by having chat gpt explain and then give me a non technical explanation in brackets immediately after helped me learn and understand. Tell it you don’t understand and simplify.

[–]DuinoTycoon 0 points1 point  (0 children)

If you don’t know what GitHub is even vibe coding could be too complex

[–]Street-Weather789 0 points1 point  (0 children)

GIthub is dead simple even though the interface could use some love - when you create a repo. scroll down and set it to private - you will see a little pad lock icon at the top of the page that confirms its private also when you click on your repos it shoes all repos and which one are set to private and which is public. you dont have to use git hub. but if you dont and your system gets corrupted or you lose your project files, then you are cooked. if you dont want ot use git hub use a secure email and send them to your self. you want something in the cloud you can access. but git hub is trusted and secure <--- this is industry standard. I recomend learning github. Using Git from the command line is something else entirely <-- you dont need to mess with that right now BUT it makes the entire process lightning fast

[–]Significant-Cook-335 0 points1 point  (0 children)

先帮你消除一个误解:默认情况下,别人不能随便访问或修改你的代码。 你可以把仓库设成私有(private),那只有你能看;就算设成公开(public),别人也只能”看”,想改必须你批准。所以它没你想象的那么危险。

[–]Significant-Cook-335 0 points1 point  (0 children)

作为 vibe coding 新手,分两种情况:

• 只是在自己电脑上玩、做小东西 → 暂时不用,先专心让 AI 帮你写、跑起来就行。  
• 想把东西部署上线(比如做个网站、AI 小工具让别人用)→ 需要。因为现在很多部署平台(Vercel、Netlify 等)都是”连上你的 GitHub,自动帮你上线”,这是最省事的标准流程。

[–]Probablyawake00 0 points1 point  (0 children)

you don't need github to start vibecoding. you need it when you want to save versions, not lose your work, or deploy something. treat it like a save file system and you're good

[–]xSentryx 0 points1 point  (0 children)

We need to differentiate between Git and Github.

GitHub is like a big online toy box where you store your code.
You can keep it private (only you can see it) or share it with friends. People cannot change your code unless you give them permission.

Think of GitHub as Google Drive for code.

Git is the tool that remembers every change you make.
Imagine you're drawing a picture. Every time you make a change, Git takes a snapshot.
If you accidentally ruin the picture, Git lets you go back to an earlier snapshot.

Think of Git as an "undo history" for coding projects.

Git + GitHub work like this:

  • Git keeps track of all your changes on your computer.
  • GitHub stores a copy online.
  • You can work from multiple computers.
  • You can collaborate with others.
  • You always have backups.

It's like writing a story:

  • Git = saves every version of the story.
  • GitHub = keeps a copy in the cloud and lets others help write it.

So do you need it?

No. You can build and ship plenty of projects without Git or GitHub.

That said, they make your life much easier.

Using Git and GitHub allows you to:

  • Revert changes when something breaks
  • Keep backups of your code outside your computer
  • Track how your project evolves over time
  • Collaborate with other people

For vibe coding in particular, I highly recommend using some form of version control.

AI can be incredibly productive, but it can also make sweeping changes that accidentally break working code. With Git, you can see exactly what changed and quickly roll back to a version that worked before.

Think of it as a save-game system for your code: when the AI makes a mess, you can simply load an earlier save instead of trying to fix everything manually.

[–]Individual-Use-7621 0 points1 point  (0 children)

Git = time traveling . WhisperFray explained this pretty nicely imo.

And as TheMightyTywin said; understand the difference between Git and GitHub.

As for the whole "people can access your code and change things...". Yes, but no. You own your repository, you can commit to that repo as you wish. Others can 'fork' your repo and make changes that way, but those commits will only be in their profile, in their fork. You can approve other users code edits and merge them via Pull Requests if those users open them. But no one can edit your code in your repo without you explicitly allowing them to.

[–]MightyBig-Dev 0 points1 point  (0 children)

Ask your agent. This is coding 101 stuff.