Your builder path
6 / 6 chaptersThis chapter
Step 1 of 3Your next action
Save to GitHub
Get your project off your machine
Create an empty repository, then run the commands in this step to push your project. Check that no secret, token or private key goes with it.
Open for this step
Need a hand?
If GitHub is blocked, keep your local proof and move to the next step. A screenshot of a working build still counts.
For this step
Never commit a secret
Anything committed stays in the history even after you delete the file. Check
that no .env file, key or password is in the list before you commit.
Create an empty repository on GitHub with the same name as your folder, then run these in your project terminal:
git init
git add .
git status
git commit -m "First working build"
git branch -M main
git remote add origin https://github.com/USERNAME/REPO-NAME.git
git push -u origin mainSwipe sideways if a command is long.
Read the output of git status before committing: every file it lists is about
to be uploaded. Then refresh the GitHub page and confirm your files are there.
For this step
On Vercel choose Add New, then Project, import the repository you just pushed, leave the settings alone, and press Deploy. When it finishes, open the live link and use the main action there, not in your local preview.
| If this is blocked | Use instead |
|---|---|
| Vercel | GitHub link plus a screenshot |
| GitHub and Vercel | A short screen recording of the main action |
Proof is flexible. Publishing is the strongest form of it, never a required one.
For this step
Answer these five out loud, in about a minute, with the build on screen:
- Who is this for?
- What is the one thing it does?
- What did you test, and how?
- What broke, and what did you fix?
- What would you build next?
Your folder is reusable. The next build starts with the same starter, a new brief, and a coach that already knows the loop.
Before you move on
Common mistakes
- Pushing a
.envfile or a key becausegit statuswas never read. - Sharing the localhost address, which only works on your own machine.
- Skipping the live-link test because the deploy reported success.
- Explaining the code instead of the user and the proof.
Work through one step at a time. Ticking a step marks it for this page view only, so nothing is saved when you leave.