Theo-brainUnofficial. Not affiliated with Theo or t3.gg.
Sign inYou

De-risking the merge button

Technique

Make merging safe on two fronts. Code should be very likely fine before a person approves it. Mistakes that slip through should do little damage, because they reach a few users first and are easy to revert (undo).

Theo's current stance

This is how Theo 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

  1. Ask your agent to set up releases that go to a limited group of users first.
  2. Make reverting a bad change a quick, routine step.
  3. 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

Anthropic Rebuilt Git (yes really)

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

Anthropic Rebuilt Git (yes really)

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

Anthropic Rebuilt Git (yes really)

Theo Daily is unofficial and not affiliated with Theo or t3.gg. Written by Claude Opus 5.5 from each video's transcript.