Measure whether the evaluation pull request works

Translate the claim into assertions or a tiny eval harness. The metric to protect is: gh pr view shows base=main, head=improve-evaluation, and check summary. Always record the denominator (how many cases) beside any rate. A percentage without a denominator is marketing, not measurement.

gh pr view --json baseRefName,headRefName,statusCheckRollup --jq '{base:.baseRefName,head:.headRefName,checks:(.statusCheckRollup|length)}'

Expected evidence: base main, head improve-evaluation, checks count. A passing assertion proves only the behavior it names; broader usefulness still needs the chapter’s full limits.

Be explicit: beating the baseline (branch protection / required checks listed before opening the PR) on this fixture does not prove behavior under pushing straight to main, or opening a PR with failing checks ignored. Label observations separately from conclusions so the next page inherits honest evidence about the evaluation pull request.

Compute gh pr view shows base=main, head=improve-evaluation, and check summary 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 branch protection / required checks listed before opening the PR before celebrating.

Add one negative case aimed at pushing straight to main, or opening a PR with failing checks ignored. A suite with only happy cases cannot protect the evaluation pull request when the characteristic failure appears in review.

If a check is expensive or flaky, shrink it until it is deterministic on feature branch improve-evaluation with one commit. 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 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 metrics with explicit denominators and a negative case 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

For github-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 github-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 github-basics, write a transfer example that differs in one constraint from the chapter scenario. Keep the quality bar fixed. Explain which check still applies.