Skip to content

03-github.md

Latest commit

 

History

History
183 lines (117 loc) · 5.42 KB

03-github.md

File metadata and controls

183 lines (117 loc) · 5.42 KB

🗂️ SECTION 2 — GitHub Without the Fear

GitHub scares a lot of beginners. It shouldn't. It's just a place to save your code and see what changed.

Here's the good news: Firebase Studio creates your GitHub repo for you automatically. You don't need to set it up manually.

This section removes the fear and shows you how GitHub works (and how Firebase Studio makes it easy).

Lesson 2.1 — GitHub Explained Like You're 5

What GitHub Actually Is

GitHub is like Google Drive for code.

  • You save your project there
  • You can access it from anywhere
  • You can see what changed
  • You can go back to old versions

That's it. No magic. No complexity. Just a place to save your code.

Repos = Project Folders

A repository (repo) is just a folder for your project.

Think of it like:

  • A folder on your computer = A repo on GitHub
  • Your project files = Your code files
  • Your README = Your project notes

Creating a repo is like creating a new folder. That's all.

Commits = Save Points

A commit is like saving your game.

  • You make changes to your code
  • You "commit" (save) those changes
  • GitHub remembers what changed
  • You can go back to any save point

It's version control, but think of it as "save points" and it makes sense.

Why GitHub Matters Even If You're Not a Dev

You might think: "I'm not a developer, why do I need GitHub?"

Here's why:

  1. Your code is safe — If your computer dies, your code is still on GitHub
  2. You can see progress — Look back at what you built and when
  3. You can work anywhere — Access your project from any computer
  4. It's your project's memory — See what changed and why
  5. It's professional — Even if you're a beginner, using GitHub shows you're serious

You don't need to be a developer to benefit from GitHub. You just need to build things.

The Mental Model

Think of GitHub like this:

Your Computer          GitHub
─────────────         ────────
Project Folder   →    Repository
Save File       →    Commit
See Changes     →    View History

Same concepts, different names. Don't let the terminology scare you.

Lesson 2.2 — How Firebase Studio Creates Your Repo (The Easy Way)

Firebase Studio Does It For You

Here's the magic: You don't manually create a GitHub repo. Firebase Studio does it for you.

When you publish/sync your code from Firebase Studio:

  1. Firebase Studio will prompt you to connect to GitHub
  2. It will ask you to create a repo name (like my-note-app)
  3. Firebase Studio automatically creates the repo on GitHub
  4. Your code gets synced to that repo automatically

That's it. No manual setup. No confusion. Firebase Studio handles it.

Note: You can always create a GitHub repo manually first if you prefer. But for vibe coding, we use the Firebase Studio automatic approach because it removes friction and gets you building faster. That's the vibe coding way.

What You Need to Do

Before Firebase Studio can create your repo:

  1. Create a GitHub account (if you don't have one)

  2. Connect GitHub to Firebase Studio

    • When Firebase Studio asks to connect, authorize it
    • This lets Firebase Studio create repos for you

That's all the setup you need. Firebase Studio does the rest.

Naming Your Repo

When Firebase Studio asks for a repo name, use something descriptive:

Good names:

  • my-note-app
  • habit-tracker
  • idea-saver
  • resource-bookmarker

Bad names:

  • project
  • test
  • new-thing
  • asdfghjkl

Rule: Name it what it does, not what it is.

Keep Your Repos Private (Important!)

When Firebase Studio creates your repo, make it private.

Why?

  • Your code is yours (you might not want it public)
  • You might have API keys or sensitive info (we'll cover .gitignore later)
  • Private repos are free on GitHub

How to make it private:

  • When Firebase Studio asks, select "Private repository"
  • Or change it later in GitHub settings

Don't commit secret keys or sensitive information. We'll learn about .gitignore later to handle this properly.

What Happens After Firebase Studio Creates Your Repo

Once Firebase Studio creates your repo:

  1. Your code is on GitHub (safe and backed up)
  2. You can clone it to your computer
  3. You can open it in Cursor
  4. You can work on it locally
  5. You can commit changes and push them back

Firebase Studio made it easy. Now you can use GitHub like a pro.

Using GitHub as a Project Map

GitHub isn't just for saving code. It's for tracking your project.

Your commits tell a story:

  • "Added user authentication"
  • "Created note saving feature"
  • "Fixed login bug"
  • "Added delete functionality"

Each commit is a milestone. Together, they're your project's history.

🎯 Action Step

Before you build your first app:

  1. Create a GitHub account (if you don't have one)

    • Go to GitHub.com
    • Sign up (it's free)
    • Verify your email

  2. That's it! Firebase Studio will handle the rest when you publish your first app.

You don't need to create a repo manually. Firebase Studio will do it for you when you sync your code.

This is the vibe coding way: Remove friction. Let the tools do the setup. Focus on building, not configuring.

Next: SECTION 3 — Cursor: Your AI Co-Builder