GitHub for Vibe Coders — From Zero to First Push

What You'll Learn

By the end of this guide, your vibe coded project will be on GitHub with automatic deployments. Every push deploys your app. You'll never lose code again.

Time: ~20 minutes Prerequisites: A Bolt or Lovable project you want to deploy

Step 1: Create Your GitHub Account

Go to github.com and sign up. Use a professional username — it's public and appears on your code.

After creating your account, you should see your empty profile page. That's your checkpoint.

Step 2: Export Your Project

From Bolt.new: Click the GitHub icon in the toolbar → Connect GitHub → Create new repository → Name it (e.g. my-saas-app) → Push.

From Lovable: Click the GitHub icon in top right → Connect GitHub → Create repository → Enable two-way sync.

From Cursor (existing project):

cd your-project
git init
git add .
git commit -m "Initial commit"
gh repo create my-project --public --push

Install GitHub CLI if you don't have gh.

Checkpoint: Your repo appears at github.com/your-username/your-repo with all your files.

If GitHub authorization fails in Bolt, disconnect and reconnect GitHub in Bolt settings.

Step 3: Understand Your Repository

Your GitHub repository has:
• Code tab — all your files
• Commits — every saved version (your undo history)
• Actions — automated workflows (CI/CD)
• Settings — where you connect Vercel/Railway

Click "Commits" to see every change ever made. This is your safety net.

Step 4: The 4 Git Commands You Need

After making changes in Cursor, run these to save them to GitHub:

# Save your current changes
git add . && git commit -m "Add payment feature"

# Upload to GitHub (triggers auto-deploy)
git push

# Download latest changes
git pull

# Undo last commit (keep changes)
git reset --soft HEAD~1

Good commit messages describe what changed:

# Good
git commit -m "Add Stripe checkout flow"
git commit -m "Fix login redirect bug"

# Bad
git commit -m "update"
git commit -m "fix"

Commit after every feature that works. Think of it as hitting Save in a video game.

Checkpoint: After git push, refresh github.com — your latest changes appear.

If you get "error: failed to push some refs", run git pull first, then git push.

Step 5: Connect to Auto-Deploy

Connect your GitHub repo to a hosting platform so every push deploys automatically:

Vercel: vercel.com → New Project → Import from GitHub → Select repo → Deploy. Every push to main = new production deploy.

Railway: railway.com → New Project → Deploy from GitHub → Select repo → Deploy. Same result.

Checkpoint: Make a small change, git push, wait 60 seconds — your live URL updates automatically.

Next Steps

Deploy to Vercel — detailed guide with env vars and custom domains

Deploy to Railway — for apps needing a persistent backend

Buy a domain — connect your own domain