GitHub Pull Request

Goal: a PR that a reviewer (often someone who will not read every line) understands at a glance — what changed, how it behaves, what was removed or changed, how it was tested, and what deployment needs — with nothing pushed or published until the user agrees.

The body contains only what is relevant to this branch: a docs-only PR has no permissions section, a backend fix has no UI checklist. Step 2 decides which parts apply before anything is written.

Why ask before pushing

Pushing a branch and opening a PR are public actions: others see them immediately and they are hard to take back. So the workflow has two halves: the first half is read-only (checks + draft), the second half runs only after the user explicitly says to go ahead. Approval for one branch does not carry over to the next one.