Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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

Daksh Gupta profil fotoğrafı
Daksh Gupta2 ay önce

more here -

grim profil fotoğrafı
grim2 ay önce

fuck yes!!!

Ankan🧊 profil fotoğrafı
Ankan🧊2 ay önce

Tried T-Rex, and its goated

Onkar Hanchate profil fotoğrafı
Onkar Hanchate2 ay önce

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

max.berlin profil fotoğrafı
max.berlin2 ay önce

Oh damn Oh damn Oh damn this is sickkkk

Caio Lins profil fotoğrafı
Caio Lins2 ay önce

love what you guys are up to 🪴

Daryl profil fotoğrafı
Daryl2 ay önce

Need that TREX dance now

Gregor profil fotoğrafı
Gregor2 ay önce

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

Mahendra Kumawat profil fotoğrafı
Mahendra Kumawat2 ay önce

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

Matjussu profil fotoğrafı
Matjussu2 ay önce

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.

Subramanya N profil fotoğrafı
Subramanya N2 ay önce

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

Benzer Videolar