Andrew McCarron

Andrew McCarron

Founder @ Koalr. Deploy risk scoring.

About

20+ years in software delivery. Built Koalr after watching too many teams ship dangerous deploys they could have caught. Obsessed with pre-merge risk, blast radius modeling, and making deployment intelligence accessible to every engineering team.

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking
Gone streaking 5
Gone streaking 5

Forums

What signals do you actually check before merging a high-stakes PR?

Most teams have an informal mental checklist PR size, who wrote it, whether tests passed, time of day. But it's rarely written down, and it varies by person.

Curious what signals matter most to your team before you merge something you're nervous about. Is it coverage? CODEOWNERS sign-off? Who's on call? Something else entirely?

Koalr - Deploy risk scoring for every PR — before it merges

Koalr scores every PR 0–100 for deploy risk using 36 signals — coverage delta, file expertise, change entropy, SLO burn rate, and more. Plus blast radius propagation, proactive AI briefings, autonomous reviewer, DORA metrics, and 23 integrations.

We let Claude write 100% of our code for 7 days. Here's what broke first.

Last week we did something stupid.

We paused all human coding. Gave Claude (Anthropic) access to our GitHub repo. Told it to build new features, fix bugs, and ship.

No human review. No guardrails. Just Claude and our codebase.

For 7 days, it ran the engineering team.

View more