+1 to this enhancement! We force everyone to squash and merge PRs in our repo so the individual commit messages within the PR are just for the PR author. All the squashed commits aren't relevant in the final commit description, so we would rather just automatically use the PR description. Thanks!!
When using GitHub pull request template, it does not make much sense to use description nor does it make sense to get a list of all the commits.
I would love it if I can just to the default behavior to be blank!
Perhaps something configurable in the .github folder?
Or once GitHub workflow becomes publically available, I can automate the behavior myself.
I would totally love to be able to automatically disregard commit history message in squashed commit - now we are forced to do that with every merge!
This extension will remove the commit message 💪 Hope you find it useful @zuzusik
For my use case, even just a checkbox option that lets you treat all PRs as if they have multiple-commits would suffice.
I made a browser extension to use the PR description as the squash and merge commit message.
This may be a tad different than what's requested but the simple ability to edit the commit message would be great. We use a tool to generate release notes from our commit log and it's messy if a PR has multiple commits and not all the commit messages were written correctly. The squash & merge just concatenates all the messages but it would be nice to be able to pick one.