GitHub & Vercel · 01 / 02
Publish to GitHub
Back up your project and create shareable source proof. Create a repository in the browser, then push from your project folder with one command card.
Publish to GitHub
What this is
GitHub is where your project lives online. In this workshop it does two jobs: it backs up your build, and it gives you shareable source proof that you made it. It is shared by both Vibe 101 and Vibe 102.
Why it matters
A project only on your laptop can be lost. A project on GitHub can be restored, shared, and connected to Vercel for a public link. It is also the cleaner way to prove the work is yours than a single screenshot.
What to do
Create the repository in the browser
- Create a GitHub account, or log in.
- Create a new, empty repository (no README, no template).
- Copy the repository URL.
Push from your project folder
Open the terminal inside your project folder and run this command card. Replace YOUR_GITHUB_REPOSITORY_URL with the URL you copied.
git status
git add .
git commit -m "Build first Vibe SDD project"
git branch -M main
git remote add origin YOUR_GITHUB_REPOSITORY_URL
git push -u origin mainSwipe sideways if a command is long.
If Git replies remote origin already exists, stop and ask your AI or tutor before changing it. Do not guess.
Keep secrets out of the repository
- Run
git statusfirst and read what you are about to commit. - Do not commit
.env, API keys, passwords, private data, or screenshots that contain secrets. - Do not paste secrets into ChatGPT, V0, or Antigravity prompts.
Common mistakes
- Creating the repository with a README, then hitting a push conflict.
- Committing a
.envfile or an API key. - Running the command card outside the project folder.
- Overwriting an existing remote without asking.
Next step
Put your project online with a public link on Vercel.