4 ms·
We've been using this for a few months to manage pull request merges for our mono repo. It's greatly improved the merge process. It makes trunk based releases f
by zabil 3y ago
We've been using this for a few months to manage pull request merges for our mono repo. It's greatly improved the merge process. It makes trunk based releases faster and reliable. Kudos to the team for adding this feature.
- kami8845 3y agoSame here, the experience has been generally favorable.
- ploxiln 3y agosame ... it was pretty flaky early on, got stuck, double commits, not configurable merge-group size ... but it's pretty good now
- alwaysbeconsing 3y agoIf you do squash merges, how does the queue handle the creation of the final commit message? We already have a problem with trash-filled message bodies with GitHub, and I don't want this to make it worse.
- zabil 3y agoWe turned on squash only merges and use the pull request description as the commit message. GitHub creates a temporary merge branch with the commit where you can run tests before the merge. So in the end it’s just one commit.