Pull Request to Production: the path your change takes

Pull Request to Production: the path your change takes A workflow diagram generated by Archify. 01 / You 02 / Automated Checks 03 / Human Review 04 / Merge + Stage 05 / Production EX / Blocked + Rework Propose Verify + review Merge + ship Blocking gates Recovery path Draft Change · local branch · You › Propose Draft Change local branch Pull Request · small, scoped diff · You › Propose Pull Request small, scoped diff CI Suite · lint, unit, contract · Automated Checks › Blocking gates › Verify + review · blocking CI Suite lint, unit, contract blocking Preview Env · per-PR deploy · Automated Checks › Blocking gates › Verify + review Preview Env per-PR deploy Code Review · codeowner approval · Human Review › Verify + review · human gate Code Review codeowner approval human gate Merge Queue · rebase + re-test · Merge + Stage › Merge + ship Merge Queue rebase + re-test Staging Soak · synthetic traffic · Merge + Stage › Merge + ship Staging Soak synthetic traffic Canary Release · 1% then 100% · Production › Merge + ship · production Canary Release 1% then 100% production Send Back · red check or request · Blocked + Rework › Recovery path › Verify + review Send Back red check or request Revert · last good digest · Blocked + Rework › Recovery path › Merge + ship · owner: on-call Revert last good digest owner: on-call triggers checks green reviewable build approved merged to main SLOs hold red push a fix restore digest Legend User UI Agent logic Policy Tool action Cloud service

Keep the path short

  • • A scoped diff clears review and the merge queue faster
  • • Preview environments move review from reading to trying
  • • The merge queue re-tests against main, not against your base

Where changes stop

  • • A red check sends the change back before review time is spent
  • • Codeowner approval is a human gate, not a formality
  • • Staging SLOs decide whether the canary starts at all

Know before you merge

  • • Who is on call for the service you are touching
  • • Which flag, if any, gates the new behaviour
  • • How to revert: a digest restore, not a new build