Measure whether the focused Git commit works

Translate the claim into assertions or a tiny eval harness. The metric to protect is: git diff --cached --name-only shows only train.py before commit. Always record the denominator (how many cases) beside any rate. A percentage without a denominator is marketing, not measurement.

git show --stat --name-only HEAD
git status --short  # README still dirty

Expected evidence: HEAD has train.py; README unstaged. A passing assertion proves only the behavior it names; broader usefulness still needs the chapter’s full limits.

Be explicit: beating the baseline (git status and git diff before any add) on this fixture does not prove behavior under accidentally staging both files, or committing from the wrong directory. Label observations separately from conclusions so the next page inherits honest evidence about the focused Git commit.

Compute git diff --cached --name-only shows only train.py before commit with the denominator written beside the rate every time. For this chapter, the evaluation set is intentionally tiny; that is allowed only if you say so in the evidence. Compare against git status and git diff before any add before celebrating.

Add one negative case aimed at accidentally staging both files, or committing from the wrong directory. A suite with only happy cases cannot protect the focused Git commit when the characteristic failure appears in review.

If a check is expensive or flaky, shrink it until it is deterministic on repo with dirty train.py (eval) and README.md (docs). Flaky green builds teach the team to ignore gates. Record what this page does not prove so security-ops and mastery-ship inherit honest limits.

At the evaluation stage for git-basics, the job is narrower than finishing a product demo. You are creating one progressive evidence piece about repo with dirty train.py (eval) and README.md (docs) that later pages inherit without redefining success. Keep that fixture small enough to inspect by hand, keep outputs copy-pasteable as text, and refuse to narrate this baseline as if it were a production SLA: git status and git diff before any add.

For this page specifically, success looks like metrics with explicit denominators and a negative case while still centering the user decision to land only the tested train.py evaluation change while README edits stay unstaged. If you cannot point to a file, command, or assertion that proves that for the focused Git commit, stay on this page instead of advancing.

Git glossary

Previous · Next

For git-basics, write a transfer example that differs in one constraint from the chapter scenario. Keep the quality bar fixed. Explain which check still applies.

For git-basics, write a transfer example that differs in one constraint from the chapter scenario. Keep the quality bar fixed. Explain which check still applies.

For git-basics, write a transfer example that differs in one constraint from the chapter scenario. Keep the quality bar fixed. Explain which check still applies.

For git-basics, write a transfer example that differs in one constraint from the chapter scenario. Keep the quality bar fixed. Explain which check still applies.