GitHub for Vibe 101
What this is
This is the Vibe 101 checkpoint for saving your project code on GitHub.
Use the full GitHub reference if you need a deeper explanation.
Why it matters
Vercel deploys from GitHub. If the latest code is not pushed, the live site will not match the project you tested on localhost.
GitHub also gives your tutor a clean link to inspect when you need help.
What to do
Step 1 — Do these manually in the browser
These steps need you, not the AI agent:
- Open github.com.
- Log in or create a GitHub account.
- Click New repository.
- Name the repository after your project.
- Keep it simple: choose Public unless your tutor says otherwise.
- Do not add README,
.gitignore, or license if your project already has files. - Click Create repository.
Keep the GitHub page open. You will need the repository URL.
Do not paste your GitHub password, recovery codes, or tokens into AI chat.
Step 2 — Ask AI to guide the terminal push
Use this in the IDE after the repository exists:
Help me push my local project to GitHub step by step.
Important:
- Do not ask for my password, token, or private key.
- Use the integrated terminal in my IDE.
- Check the current folder first.
- Explain each command before I run it.
My GitHub repository URL is:
[paste repository URL]
Before pushing, check:
1. I am in the correct project folder
2. package.json exists
3. node_modules is not being committed
4. git status is safe to review
Then guide me through:
1. git init if needed
2. git add
3. git commit
4. adding the remote repository
5. pushing to GitHub
6. checking the files onlineRun the commands one by one. Read the AI explanation before pressing Enter.
Step 3 — Confirm the push worked
Refresh the GitHub repository page.
You should see files like:
package.jsonsrcorapppublic- config files such as
next.config
If you do not see the files, stop and fix GitHub before going to Vercel.
If something goes wrong
Use this prompt:
My GitHub push is not working.
Command I ran:
[paste command]
Terminal output:
[paste exact error]
What I expected:
My project files should appear in my GitHub repository.
Help me fix this one step at a time.
Do not ask for my password, token, private key, or recovery codes.Ask your tutor if GitHub says the repository does not exist, you are logged into the wrong account, or permissions are blocked.
Common mistakes
- Using the wrong GitHub account.
- Creating the repository in the browser but forgetting to push from the terminal.
- Pushing to the wrong repository.
- Forgetting to push the latest code before deploying.
- Uploading files manually instead of learning the push flow.
- Pushing
node_modules. - Pasting tokens or passwords into AI chat.
Vibe 101 / Current checkpoint
GitHub Checkpoint
Ready to stamp - Saved in this browser only.
0 of 20 checkpoints complete.