Classes 10–12: Get the course’s latest changes
Your task-app is a fork of the course’s copy of the app, y-rosenthal/yr-2026-full-stack-demo: a copy of it as it was on the day you forked it. When I fix or improve the course’s copy, your fork doesn’t change by itself. When I announce a change, do the steps on this page to bring it into your fork and onto your computer, then do whatever else the announcement says.
Time: about 5 minutes, plus whatever the announcement asks for.
As of Oct 22, 2026 · Official docs: GitHub: Syncing a fork · git pull · Vercel: Deploying from Git
There are three copies of the code, and the change has to reach the last two:
y-rosenthal/yr-2026-full-stack-demo the course's copy, on GitHub ("upstream")
│ 1. Sync fork (on GitHub's website)
▼
YOUR-USERNAME/task-app your fork, on GitHub ("origin")
│ 2. git pull (in your terminal)
▼
~/projects/full-stack-demo-app/task-app your copy, on your computer1. Check that your own work is saved
In VS Code’s terminal, first go into the app’s folder (harmless if you’re already there; this just makes sure):
cd ~/projects/full-stack-demo-app/task-appThen type:
git statusIf it says nothing to commit, working tree clean, go on to step 2. (Your .env.local file doesn’t count: Git ignores it, so it never shows up here, and the update never touches it.)
If it lists changed files, you changed the app’s code yourself. Save that work first with a commit, as in (J) Save your work to GitHub. If you don’t know why a file changed, ask Claude (When you’re stuck) before you go on: paste what git status printed.
2. Update your fork on GitHub
- Open your fork,
https://github.com/YOUR-USERNAME/task-app(with your own GitHub username). - Above the list of files, GitHub says whether your fork is behind the course’s copy, for example “This branch is 2 commits behind y-rosenthal/yr-2026-full-stack-demo:main”.
- Click Sync fork, then Update branch.
If it says your branch is up to date, there’s nothing to sync. If GitHub offers to Discard your commits, don’t click that: your fork has changes of its own that conflict with mine. Take a screenshot and ask Claude or me for help.
3. Bring the changes onto your computer
In the same terminal, in the task-app folder, type:
git pullgit pull downloads the new commits from your fork on GitHub and adds them to your copy. It lists the files that changed, for example supabase/migrations/1_init_tasks.sql. If it says Already up to date., your fork wasn’t synced yet: go back to step 2.
If it refuses, with a message such as “Your local changes to the following files would be overwritten by merge”, go back to step 1: a file you changed is also changed by the update.
4. Do what the announcement says
Getting the new code onto your computer doesn’t change your Supabase project or your website by itself. The announcement says which of these to do, in the task-app folder:
| If the change is in | Then type | What it does |
|---|---|---|
supabase/migrations (the database) |
npx supabase db push |
Applies the new or fixed migrations to your Supabase project, as in (G) |
supabase/functions (an Edge Function) |
the npx supabase functions deploy ... line for that function |
Uploads the new version of the function, as in (H) |
package.json (the list of packages) |
npm install |
Installs the new packages, as in (B) |
the web pages (app, components, hooks) |
nothing, if npm run dev is running |
The development server reloads the pages by itself |
If your app is already online (Step K), Vercel notices the new commits in your fork on GitHub and puts the new version online by itself.