The short answer
It overlaps with file storage but adds commits, branches and collaboration. Public content can be copied, so keep private material out of practice repositories.
Try it in three steps
- Inspect a repository's root structure.
- Find the history and inspect a change.
- Separate source files, generated outputs and documentation.
A practice prompt
Before you start
Use fictional files and history without creating an account.
Practice material (fictional)
Files: README.md, src/main.js, tests/check.js. History: add documentation, then fix input validation.Replace placeholders in the prompt with this material, or append the material if there are no placeholders. Reading time excludes doing the exercise.
Identify source, documentation, tests and build outputs: files produced by turning source into runnable or publishable forms. Mark unclear folders unknown and do not suggest deletion.What to look for (not a recorded test result)
README documents the project; src and tests suggest code and tests, subject to inspection. History explains changes beyond the current files.
If it goes wrong
Do not delete unfamiliar files because there are many of them; investigate their purpose.
Check your result
You understand that a repository tracks changes as well as current files.
References and scope
The links below support the concepts or product navigation. The steps and exercises are our teaching suggestions, not official certification or measured customer outcomes. Product interfaces and availability may change. References checked on 2026-10-17.