Lesson 16 / 25

Pull request descriptions

Use Pull request descriptions to make a clear, evidence-based decision.

Understand Pull request descriptions

Start by naming the decision behind Pull request descriptions. A strong answer explains the goal, the constraints, and the evidence you would use before acting. Do not treat a checklist as understanding: connect each step to the outcome it protects.

Keep the workflow visible

Use this simple path while practising Pull request descriptions: understand the situation, make one deliberate choice, then review the result.

A four-stage workflow for Pull request descriptions.
Figure 4.1 — Decide, act, check and improve.

A useful comparison

Think of Pull request descriptions like planning a journey: a destination without a route is only a wish, while a route without a destination wastes effort.

Check the decision, not just the terminology.

Quick check: What is the most useful way to apply Pull request descriptions?

  • State the goal, constraints and evidence before choosing an action.
  • Copy a template without checking whether it fits.
  • Use the most complex option first.
Answer

State the goal, constraints and evidence before choosing an action. — Good practice makes the reasoning visible, so you can review and improve it.