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.

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

> 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.