Squash commits when merging #6484
Marcono1234
started this conversation in
Ideas
Replies: 1 comment
-
Would still be interested in your opinion on this because I think all of this still applies. One additional issue is that usually within a PR the commit messages are specific to that PR, e.g. "Add change note", which is perfectly fine, but in the history of Another disadvantage might be that the repository size increases faster when not squashing the commits. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Most or all pull requests against this repository are currently merged with a merge commit. This makes the Git history of
main
rather verbose and possibly difficult to navigate:main
)Have you considered squashing commits when merging pull requests? Or is there a reason why you refrain from doing this?
This would probably lead to a cleaner Git history on the main branch.
Note that I am not blaming the pull request authors for making typos or other mistakes, I am just questioning whether there is any value in having separate commits for them on the
main
branch.Similarly I am not suggesting to squash commits of all pull requests. There are situations, especially for large pull requests, where it is desired to keep the separate commits on the
main
branch.Beta Was this translation helpful? Give feedback.
All reactions