Put a Project Under Version Control
Turn a friend's messy website folder into a clean repository: keep a token, downloaded packages, build output, a log and OS junk out with .gitignore, commit the site in small steps with first lines people can read, and fix a typo in its own commit. A local self-check verifies the history and writes your submission for instant, rubric-based feedback.
40 min
Est. time
3
Outcomes
5
Rubric criteria
60%
Pass score
What you'll learn
Skills you'll have real reps in after shipping this.
The scenario
Your friend Ana keeps her recipe website in a plain folder. There's no history, so every change is a gamble, and the folder holds files that should never be shared: an analytics token in .env, a node_modules folder of downloaded packages, a dist folder of build output, a log, and the .DS_Store file a Mac leaves behind.
She asks you to put it under version control properly before she shares it. You'll make a repository, keep the junk out, commit the site in a few small steps with messages someone can read next year, and fix the typo in her pancake recipe in its own commit.
Your role
You are the friend who knows Git. Your deliverable is a clean repository: a committed .gitignore that keeps out all five kinds of junk, a history of at least four focused commits with clear first lines (one with a body that explains why), the typo fix as its own commit, and a short note on what you kept out and why.
Start the task to unlock the full brief
You'll get the step-by-step requirements, setup commands, the 5-criterion grading rubric, tips, and the ability to submit your solution for instant AI grading.
Free to start · submit when you're ready
Learning resources
Put a real project under version control, hands-on
The best first Git project is a messy real folder. This kit gives you one: a small recipe website with no history, plus the files that trip up beginners, an analytics token, downloaded packages, build output, a log and a macOS .DS_Store. You set up the repository, write the .gitignore before the first commit, commit the site in small steps with messages someone can actually use, and fix a typo in its own commit. A local self-check reads your history and writes your submission only when everything genuinely passes. It is the first graded project in Preporato's Git course.