Pathwise

Manuals / CI/CD Pipelines / Chapter 9

D · Governance · advanced · Week 6–7 · Chapter 9 of 12

Required checks & merge gates

Branch protection + required status checks prevent merging broken code. Balance safety vs team velocity.

Path progress
69%

Step 1 of 4

Branch protection on main

Require PR, require status checks, no direct push (for team repos). Solo: still practice config.

Branch protection on mainDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →Branch protection drag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Do this now

Enable require status checks before merge. List required check names.

Was this step clear?
Chapter learning outcomes
  • Branch protection rules
  • Required status checks
  • CODEOWNERS
  • Merge queues awareness

Clear these before you leave

Side quest

Gate review

Pretend tech lead: argue to remove one check. Defend or concede.