We would have never known how many flaky tests we had exactly, or to what level each of them was flaky. Now we say it meets this level, and that's it - it's quarantined.

If you have a monorepo — or want to move to one — and you have dozens or hundreds of developers, these are the challenges you're going to face. How do you have one CI process manage all of that safely? It's complicated to do yourself. Trunk has basically solved it.

The flaky test dashboard has been super useful, allowing our team to see flaky vs broken tests, number of pull requests impacted by flaky tests, and the age and frequency of flaky tests.

Trunk Merge was a winner for us because something that used to take 30 minutes can be replaced with something that takes two.

It's really nice to be able to go into the dashboard and see—oh, this has flaked on 15 different PRs today. This is actually impacting the organization and needs to be either quarantined or fixed quickly.

I heard some comments... a week after we enabled it, and they basically told me, 'Man, you got that just in time. We had this big push to meet this milestone. A lot of people were trying to get their changes in. A lot of people were frustrated about this.

With Trunk Merge Queue, I've helped enable many aspects of our development process that would've been otherwise challenging. Now, we can easily handle a high volume of changes without compromising on stability.

Potential problems are resolved before we even commit the code... That's a big win for any team.