Squash your commits

Re:Squash your commits by WorldMaker on Friday April 01, 2016 @04:01PM (#11408066)

«Have you ever tried following a change in a repo that came from an unsquashed PR?»

I have a self-congratulating black belt in source code archeology. With the right tools, most of which are on GitHub, even, such as good commit range diffing, smart uses of tags and branches, and knowing how to navigate the DAG from merge commits (more reason to -no-ff) you have a lot of power in your hands.

«What's truly meaningful IMO is a git log that reads like a product change log»

I appreciate that point of view, but I don't share it. A product change log, I feel, is a bit of marketing/PR that needs some time, love, and editing; I find a git log is for catching snapshots of raw progress and more often useful in seeing what your co-developers are up to, as they are working.

[ Parent | on HN ]

Re:Squash your commits by kylnew on Friday April 01, 2016 @04:20PM (#11408240)

I think this really comes down to team. It's kind of an all-in or nothing thing and if you go against the grain everyone will just end up angry

[ Parent | on HN ]

Re:Squash your commits by WorldMaker on Friday April 01, 2016 @04:56PM (#11408545)

Absolutely, not every team follows the same preferences, so with any style/aesthetic choices, be sure to know what the team zeitgeist is. (I'm not a monster, I play well on teams, I promise.)

[ Parent | on HN ]

Re:Squash your commits by natrius on Friday April 01, 2016 @04:22PM (#11408253)

Try it both ways. I used to agree with you until I tried squashing after code review.

[ Parent | on HN ]