Disable merge commit in PRs - only enable squash merging to tidy up the commit history #1544
Replies: 2 comments 5 replies
-
|
I'm selective about my use of squash merging. If the author has done a great job they might have clearly distinct commits for the parts needed to implement a feature, the ability to revert a single one of those is lost if you squash. On the flip side someone has commits like "and another thing" then I will probably squash it. The Go project seem to be happy with the results of doing only rebase merging to clean up their history. |
Beta Was this translation helpful? Give feedback.
-
|
I don't want sqash commits. But I also don't want dirty commits, so in reviews I'm asking authors to do cleanups. Personally I do great care at making specific focused commits and carefully document them, amending when necessary. I don't want another maintainer to come and squash them at merge time. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I saw that the project recently has multiple PRs merged, but the commit history in master is bugging me since it has multiple merge commit that feels unnecessary

Can we just enable the squash and merge option for the repo?
like this
also please do correct me if there is a reason for this.. many thanks 🙏
Beta Was this translation helpful? Give feedback.
All reactions