Classes 10–12 (J): Save your work to GitHub

← (I) Try the app · All steps · (K) Put the app online with Vercel →

Part of the task-app setup for Classes 10–12. Work through the parts in order, doing every step yourself; Start here has the worksheet, the screenshot log, how to ask Claude when you’re stuck, and the list of all parts.

Time: about 5 minutes.

As of Oct 22, 2026 · Official docs: Git · GitHub: Pushing commits

Commit your changes and push them to your fork: type each of these commands in VS Code’s terminal, pressing Enter after each one. First go into the app’s folder (harmless if you’re already there; this just makes sure):

cd ~/projects/full-stack-demo-app/task-app

Then:

git status

git status lists the files you changed or added since your last commit, and changes nothing. Make sure .env.local is not in the list: it holds your keys, and the project’s .gitignore file tells Git to ignore it. Then:

git add -A

git commit -m "Set up the task app"

git push

What they do:

• git add -A chooses which changes go into your next commit: add stages changes, and -A (all) includes every changed, new and deleted file.
• git commit -m "Set up the task app" saves those changes as a commit, a snapshot in your project’s history. -m gives the commit its message, in quotes; write one that says what you did.
• git push uploads your new commits to your fork on GitHub.

See .gitignore and Keeping Secrets Out of Git.