Code Review vs Pul Requests
summary
Compares four concrete review workflows and what each actually enforces: git format-patch mailing lists give clean single commits and scale (Linux sees ~13,000 patches per release) but make iteration awkward; Crucible does post‑commit reviews across repositories with percent reviewed, due dates and time tracking but requires manual merges; Gerrit demands a single commit per review and encourages squash and force-push for a linear history; Bitbucket pull requests are strict branch‑to‑branch gates with CI and merge checks and multiple merge strategies (no‑ff, fast‑forward, squash).
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:47History of Code Review
- 3:25Precommit Code Review
- 5:38Mailing List Workflow
- 6:20Single Commit
- 6:47Mailing Lists
- 7:38Pros and Cons
- 14:28Garrett
- 16:05Commits
- 17:45Pul Requests
- 20:07Pull Requests
- 26:44What to use
- 27:59Summary
- 28:41Who should use which
- 30:17Questions
