Proposing changes.
WHAT THEY ARE
A proposal to merge a branch, with discussion and review before it happens.
WHAT THEY PROVIDE
Review before changes reach the main branch A record of the discussion Automated checks run against the proposal A place to link related issues
WHAT TO INCLUDE IN THE DESCRIPTION
What the change does Why How to verify it Anything the reviewer should focus on Anything deliberately left out
WHY THE DESCRIPTION MATTERS
It determines the quality of review, and it is read later when understanding the change.
WHAT TO KEEP SMALL
The change.
WHY
Large proposals receive superficial review, reliably.
WHAT TO CONFIGURE
Required review before merging Required checks passing Restricted direct pushing to main
WHAT TO AUTOMATE
Everything a tool can judge, so review addresses judgement.
WHAT TO DO AS A REVIEWER
Review promptly.
WHY
Waiting blocks the author and the change diverges.
WHAT TO DO WITH DRAFTS
Mark them, so nobody reviews unfinished work.
