239752 2022-04-25 19:56:50 -0700 Support merging pull requests containing multiple commits 2022-05-31 11:10:12 -0700 1 1 1 Unclassified WebKit Tools / Tests WebKit Nightly Build Unspecified Unspecified NEW InRadar P2 Normal --- 239082 1 emw webkit-unassigned webkit-bug-importer oldest_to_newest 1864330 0 emw 2022-04-25 19:56:50 -0700 Currently, it seems like we require PR branches to be squashed before merging. I think we should encourage contributors to write PRs with multiple commits by lifting this restriction and instead teaching Merge-Queue to do the squashing. I would expect it to use the PR description to write the squashed commit. 1866028 1 webkit-bug-importer 2022-05-02 19:57:14 -0700 <rdar://problem/92648043> 1873055 2 emw 2022-05-31 11:10:12 -0700 Real world example of where a workflow like this is needed: I'm relanding a change along with a fix. I think it's most logical, both for history and my reviewers, to land two commits: one is the automated `git revert` commit which undoes the revert, and the other applies fixes. Currently, I'm forced to squash them together. As a result, the merged commit doesn't make it clear what was changed.