git init

You're here for git init — create a repo and read status. I'll teach it the way you'd want a careful friend to teach: exact wording, walked examples, pitfalls named out loud, then checks that match this page.

You already know introductory and easy. Medium assumes those habits and asks for sharper tools — version control, search, pipes, remotes.

git init creates a .git directory that stores repository metadata. Hold that under git init: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

git status is orientation — tracked, staged, untracked, and branch name. Hold that under git init: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

Init at the project root you mean, not in $HOME or a random parent of many projects. Hold that under git init: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

Nested accidental repos confuse everyone; status "not a git repository" means wrong cwd or no init. Hold that under git init: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

Empty repos are valid; commits come after you have changes. Hold that under git init: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

Clone already brings a repo; init is for greenfield local starts. Hold that under git init: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

Default branch name may be main or master depending on config — read status. Hold that under git init: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

Treat status like pwd: run it constantly. Hold that under git init: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

Put git init in a sentence you could teach a friend: what changes, what stays the same, and what you expect from the still. Software rewards that sentence more than highlighting. If the sentence needs five caveats, tighten the model.

Open-book does not mean guess. The right answer about git init is on this page in plain language. Wrong choices are usually near-misses that sound technical; pick the claim that matches what we actually traced.

If you are skimming, stop and re-read the still for git init while pointing at each token. This is not a vocabulary flashcard — it is a behavior (or a verse's claim) you should be able to simulate aloud.

When an exercise asks you to match the still for git init, match it honestly: same names, same structure, same intent. Clever shortcuts that skip the concept will leave a hole that the next lesson falls into.

Hold git init as a behavior, not a vocabulary flashcard. Ask: what inputs matter, what action runs, what is visible afterward? If you cannot fill those three slots, you are skimming. Write them in a margin before the quizzes.

When something fails around git init, change one thing. Read the error or the wrong output. Return to the still. Do not rewrite the whole example when one token is wrong. Calm retries beat dramatic rewrites.

Compare git init with the nearest habit you already know — and name the difference out loud. Software's teaching value is often the delta: familiar idea, sharper tool.

Open-book checks for git init reward careful reading of this page. The right answer is a claim we actually made. Near-miss choices sound technical; they fail because they invert the lesson.

Before the still, predict. After the still, compare. That predict-compare loop is how git init becomes muscle memory. Passive rereading without prediction is how you forget by tomorrow.

Say a one-sentence teaching version of git init you could give a friend. If the sentence needs five caveats, your mental model is still foggy — tighten it. Precision in speech precedes precision in practice.

As you continue, git init will reappear inside larger workflows. Scripts wrap it. Branches choose it. Habits repeat it. Learning it cold now prevents cargo-cult pasting later.

Keep a scratch note for git init: one worked example, one failure you fixed, one sentence of definition. That tiny notebook beats highlighting the same paragraph five times.

If you are tired, stop at the still for git init and trace tokens with a finger. Rushing past tokens is how mysteries are born. Slow eyes make fast operators.

Wrong answers on git init quizzes are teachers too. Read the explain line. Relate it back to the still. A corrected misconception sticks harder than a lucky first guess.

git init
git status

Walk the still for git init top to bottom. Name each token. Predict the visible result. Then match the exercise honestly — same shape, same intent. Clever shortcuts that skip the concept leave a hole the next lesson falls into.

Pitfalls around git init: rushing past the still; changing five things at once when one failed; memorizing slogans without the worked example; treating open-book as an excuse not to read. Return to the still. Change one thing. Retry.

That's git init. When every quiz and exercise on this page is green, mark it passed. Next lesson when you're ready — not before the still feels obvious.