De-risking the merge button
Technique
Make merging safe on two fronts: code is very likely fine by the time a person approves it, and any mistake that slips through goes to a few users first and is easy to revert (undo).
Theo's current stance
Theo says this is how he merged 50+ pull requests in about four hours one night, timed before a nightly build he could test and pull if it was bad.
Try it
- Ask your agent to set up releases that go to a limited group of users first.
- Make reverting a bad change a quick, routine step.
- Batch changes into a regular build you personally test before it reaches everyone.
First seen
5:28
…also the other side, where if you merge something you shouldn't have, the blast radius and the damage that it can do is reduced massively by systems to make it easy to test the code once it goes out with a limited set of users, and revert the things if they do actually end up…
Every mention
5:28
…also the other side, where if you merge something you shouldn't have, the blast radius and the damage that it can do is reduced massively by systems to make it easy to test the code once it goes out with a limited set of users, and revert the things if they do actually end up…
6:51
…because I wanted to have as much in as possible for the nightly, so before I went to bed, I could download it, test it, make sure all was good, fix anything that was broken, and revoke the build if it was bad, and then go to bed smiling…
Theo Daily is unofficial and not affiliated with Theo or t3.gg. Written by Claude Opus 5.5 from each video's transcript.