Depth · Changelog
What's new
Depth ships most weeks. Here is what changed, newest first.
Try Depth on any public pull request
Paste a pull request, answer the questions its author would get after the merge, and see real feedback. No sign-up.
A reminder on the pull request
When Slack doesn't reach an author, one short comment on their merged pull request says a check-in is waiting. It never says how they answered, and teams can turn it off.
“If someone leaves”, from day one
The handover view now answers from git history before anyone has answered a check-in, and explain-backs replace the estimate module by module.
Exactly what Depth reads from your code, what it keeps and for how long, who sees what, and how to leave.
Check-ins without Slack
Every question waits on the engineer's Check-ins page in Depth. Slack is an extra way to receive them, not a requirement.
Free teams keep their check-ins
A Free team with more than five engineers keeps getting check-ins within its monthly allowance, and sees its engineer count against the plan.
Commit emails you can confirm
Engineers see every email their commits used and confirm the ones Depth could only guess; admins see the whole map in Settings.
A sturdier public scan
The bus factor scan finishes long histories, follows repositories that moved, and gives every result a link to share.
Answer in Depth, not only in Slack
Check-ins can be answered on their own page in the dashboard, with the review appearing in place.
Direct pushes count
A push straight to the default branch gets a check-in, like a merged pull request.
When someone leaves: a plan of what only they understand, handover sessions, fact-checked briefs, and successors who've shown they understand each module.
One person, every email
An engineer's commits under several emails count as one person on the map.
Merge guard
A check on pull requests showing how well the modules a change touches are understood; on Business, risky changes wait for a second person's sign-off.
Audit log
Every change to a workspace and who made it, with CSV and JSON export on Business.
Calibration week
A new team's first seven days aim check-ins at what the map is least sure about.
Self-serve plans
Team and Business, monthly or annual, with live progress while history is first read.
Explain-backs after every merge, the Understanding Map, the public bus factor scan, and the comprehension coverage specification.