Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@iiii yes, but it becomes 1 commit message with a summary of all original messages. So no matter at which line of code you inspect the commit history, you will always see the same message.
-
@fraktalisman I am guessing you sre talking about Pull Requests? Not sure what your settings are set by every repository we ever created defaults to creating a merge commit. We never use squash and merge.
Related Rants
That's a good one!
GitHub defaults to only allow squash merging feature branches, and suggests that it is "safe" to delete the feature branch that contains all the detailed commit messages at the place where they belong. Losing history, plus creating unnecessary "conflicts" after continuing to work and adding fixes to the same feature branches later.
rant
squash
merge
github