Video yükleniyor...
Video Yüklenemedi
t-rex is a new feature that spins up your stacks and runs your code to find bugs in every PR here is how we use it internally at greptile:
21,673 görüntüleme • 2 ay önce •via X (Twitter)
11 Yorum

more here -

fuck yes!!!

Tried T-Rex, and its goated

Will it be able to handle multiple layered response based bugs?

Oh damn Oh damn Oh damn this is sickkkk

love what you guys are up to 🪴

Need that TREX dance now

execution catches the easy stuff. the bugs that actually burned me needed specific user state sequences to appear, and no clean stack spin-up was gonna surface those

this is huge, can you also share how it integrates with your CI/CD pipeline?

TREX is real, not vaporware, solid feature. But running code in review isn't new, CodeRabbit already does it. The extra bug count is Greptile's own unaudited benchmark. The real complaint about Greptile has been precision, not recall: false positives, not missed bugs.

do you seed messy user states, or only run the PR against a clean stack?


