3. Work with GitHub Repositories (10-15%)
A repository is more than a folder of code — a well-built one has a small set of special files that tell both GitHub and human visitors how to treat it, a deliberate structure for how it was created and organized, and a set of built-in dashboards for judging its health. This phase covers what belongs in a repository, how to create and organize one well, and how to read the signals GitHub already gives you about it.
Think of these special files as a repository's instruction manual — leave them out, and both GitHub's own tooling and human contributors have to guess, which is exactly the gap the exam tests when it asks what a repository is "missing." ⚠️ Exam Trap: a README documents a project for humans, but only a LICENSE file makes reuse legally clear — conflating the two is a common miss.
