Hacker News Reader

Same here, the experience has been generally favorable.

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

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

same ... it was pretty flaky early on, got stuck, double commits, not configurable merge-group size ... but it's pretty good now