Mental Model & Local Setup

Before a single command makes sense, you need the picture behind it. This module gives you that picture — and then walks you through creating your very first repository, start to finish.

Why This Module Matters

Most people who "can't do Git" don't have a memory problem. They have a model problem. They memorized four commands, never learned what those commands are doing to what, and the first time something unexpected happened they froze.

So we start with the why. Why a project needs a history at all. Why a QA tester — not just a developer — benefits from one every single week. Then we set up your machine: one command to create a repository, two to tell Git who you are, and a clear-eyed look at the folder you're actually working in.

By the end of this module you'll have a real repository on your own computer that you created yourself. You'll rehearse the commands first in the First Day on the Project practice — a terminal sandbox right here, where a mistyped command costs you nothing and you can start over as often as you like — and then you'll run them for real.

What You'll Learn

• What version control is, in plain language, and what problem it solves for testers specifically
• Why test cases, environment configs, and saved logs belong in a repository
• How git init turns an ordinary folder into a tracked project, and what the .git folder is
• How git config --global user.name and user.email sign every commit you'll ever make
• What the working directory is — the files you can see and edit — and how Git watches it

A Note on the Terminal

You will be typing commands. That is the point, and it is far less scary than it looks: Git commands are short English words in a fixed order, and Git talks back to you in full sentences when something is wrong. Read what it says. It is usually telling you exactly what to do next.