Tagged: Reviews
Branch Protection Rules That Stick
Three rules cover most of the risk on main: review required, tests green, no force-push. More than that tends to get routed around.
21 October 2026 · 2 min readMerging vs Rebasing on a Small Team
Rebase to tidy your own branch, merge to combine into main. One sentence of policy saves a lot of history arguments.
21 October 2026 · 1 min readMigrations in Code Review: What to Look For
A merged migration is a fact you cannot edit. The review checklist: reversible down(), safe defaults, indexes, and no data surgery in schema changes.
21 October 2026 · 2 min readHow to Review a Large Pull Request Without Losing a Day
Sometimes the big PR lands in your queue anyway. A reading order that surfaces the risk first, and how to give useful feedback instead of a rubber stamp or a rewrite request.
21 October 2026 · 2 min readReview Your Own Pull Request Before Anyone Else Does
The cheapest review round is the one you do yourself. Read the diff as a stranger, hunt the usual suspects, and annotate the non-obvious parts.
21 October 2026 · 2 min readSmall Pull Requests Get Reviewed Faster
Review time grows faster than diff size. Splitting work into small, single-idea pull requests gets you same-day reviews and better feedback.
21 October 2026 · 2 min readTrunk-Based Development on a Small Laravel Team
Short-lived branches into main beat long feature branches: smaller merges, a main that always runs, and deploys that stay boring.
21 October 2026 · 1 min readWriting a Pull Request Description People Actually Read
What, why, and how to see it working. Three short sections beat a wall of text and speed up every review.
21 October 2026 · 1 min readReviewing Pull Requests With Git Worktrees
Run the PR next to your working copy instead of stashing and switching: git worktree, a second .env, and a throwaway database.
20 October 2026 · 1 min readCode Review Habits That Keep Main Clean
Small changes, clear descriptions and fast feedback.
15 October 2026 · 1 min read