Build the first working evaluation pull request

Build only what the claim requires: remote branch and PR exist; CI status is visible before merge. Prefer boring, deterministic code over frameworks you cannot yet explain. Run the path twice; identical output on this fixture is a feature, not a lack of creativity.

git push -u origin improve-evaluation
gh pr create --base main --head improve-evaluation --title 'Improve evaluation' --body 'Adds held-out metrics.'

Expected evidence: PR URL printed. Read each printed intermediate as part of the argument that the path works—not as decoration.

Narrate the journey from raw input to result for a single example from feature branch improve-evaluation with one commit. If you cannot name an intermediate, the implementation is still too opaque for this lab. Only after this path is solid should you generalize data sources or UI.

While implementing the evaluation pull request, print or log at least three intermediates that map to the claim (remote branch and PR exist; CI status is visible before merge). Good intermediates are values a teammate could recompute with a calculator or diff. Bad intermediates are framework traces you cannot explain.

Re-run with feature branch improve-evaluation with one commit twice. If the second run differs, either the path is nondeterministic (document the seed) or you have hidden global state—both are lab bugs until named.

Stop adding features once the path supports propose a reviewed evaluation change for merge only after checks pass. Extra UI, extra tools, or extra models belong in later chapters. The mastery bar for this page is simply: a deterministic end-to-end path with intermediates.

At the implementation stage for github-basics, the job is narrower than finishing a product demo. You are creating one progressive evidence piece about feature branch improve-evaluation with one commit 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: branch protection / required checks listed before opening the PR.

For this page specifically, success looks like a deterministic path with printed intermediates while still centering the user decision to propose a reviewed evaluation change for merge only after checks pass. If you cannot point to a file, command, or assertion that proves that for the evaluation pull request, stay on this page instead of advancing.

GitHub glossary

Previous · Next