codex-lv3-may-2025

Level Navigation: 1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18⚡

19

Level 17: Git History and Commits

User Story: As a developer, I want to have a clean git history so that I can track my progress and share my work.

What You’ll Do

Initialize git and create meaningful commits (if you haven’t already).

Instructions

If starting fresh with git:

• Initialize git repository: git init
• Create a .gitignore file (Vite creates one automatically)
• Stage all files: git add .
• Create initial commit: git commit -m "Initial commit: Complete Apple Clicker game"

If tracking changes incrementally (recommended approach):

• Make small commits after each level
• Use descriptive commit messages
• Each commit should represent one feature

💡 Code Hints

Need help with git? Check out these commands:

Initialize and first commit:

git init
git add .
git commit -m "Initial commit"

Recommended commit sequence:

git add .
git commit -m "feat: add project setup with Vite and React"
git commit -m "feat: clean up starter code"
git commit -m "feat: add game images"
git commit -m "feat: create game board structure"
git commit -m "feat: add score tracking"
git commit -m "feat: add lives tracking"
git commit -m "feat: add random apple size"
git commit -m "feat: add random apple position"
git commit -m "feat: add dynamic stats styling"
git commit -m "feat: add win condition message"
git commit -m "feat: hide apple on win"

Push to GitHub:

git remote add origin <your-github-url>
git branch -M main
git push -u origin main

✅ Check

1. Run git log --oneline to see your commits
2. Verify commit messages are descriptive
3. Check that sensitive files are in .gitignore
4. Verify node_modules/ is not committed
5. If pushing to GitHub, verify remote is set up

---