mattmatheson

Thanks! :)

We use GitHub's APIs. We did build a version before GitHub supported it, but it required using our credentials to push directly to the main branch. That wasn't acceptable to most of our customers, so we ended up not shipping it and waiting for GitHub support.

Using the GitHub APIs means you still preserve history and commit messages they way people expect (merges through the queue and direct merges behave the same), and it lets users guarantee that the only code our mergequeue merges is the code that was in the PR.

Congrats Sameen and the rest of the team! Excited to see stacks make it into GitHub.

We worked with Sameen over the last month to add support for GitHub stacks into our mergequeue, and I'm excited to announce support for it today: https://trunk.io/blog/trunk-merge-queue-now-supports-github-...

Hey there - we worked with Sameen and the team at GitHub over the past month to get support for stacks in our Mergequeue: https://trunk.io/blog/trunk-merge-queue-now-supports-github-...

They do indeed have APIs you can use in your mergequeue, I'm happy to share notes on how we built it so you can add it to your mergequeue.

How did you guys resolve merge or test conflicts? Did you just have to rebase, update your PR, and resubmit?

Mergequeues generally solve (1), but not for git merge conflicts. It's for when the combination of two in-flight changes would result in a regression (aka "logical merge conflict" https://trunk.io/blog/what-is-a-logical-merge-conflict)

> If and how our workout clothes are leaching microplastics and endocrine disruptors directly into our bodies is theoretical, though

From the linked article.

Also, I'd love to hear this from an article that isn't published by goop

"data is only useful if you can tell a compelling story"

I really like this - with this product, we're focusing on trying to tell the story and also make the data actionable. I'm hoping we can both show that there is a problem, as well as guide you to how to fix it. Otherwise, at the end of the day it's just colorful lines.

> 2. Run unit/integration/regression tests on PRs?

The blog walks through the situation where tests against a PR won't catch this.