mattmatheson

4 ms·

1.
by mattmatheson 2mo ago
Thanks! :)
2.
by mattmatheson 2mo ago
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 an
3.
by mattmatheson 2mo ago
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: htt
4.
by mattmatheson 2mo ago
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
5.
by mattmatheson 1y ago
How did you guys resolve merge or test conflicts? Did you just have to rebase, update your PR, and resubmit?
6.
by mattmatheson 1y ago
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/wh
7.
by mattmatheson 2y ago
> 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 g
8.
by mattmatheson 4y ago
"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 p
9.
by mattmatheson 4y ago
> 2. Run unit/integration/regression tests on PRs? The blog walks through the situation where tests against a PR won't catch this.
10.
What is a logical merge conflict?(blog.trunk.io)
6 points by mattmatheson 4y ago|5 comments