Fortunately, I don't squash my commits

Re:Fortunately, I don't squash my commits by SXX on Monday October 05, 2020 @07:53AM (#24686807)

I guess It's my development culture is flawed, but as one-man-team I always time constrained. So I sometimes don't have sufficient time to write too detailed commit messages.

So I end up with "one commit per feature" rather than "one commit per logical change". So I actively using squash during interactive rebase when I prepare to merge completed branch since my commit history sometimes looks like this:

   Backend: new set of APIs for XYZ
   Backend: implement feature X (+ some long comment)
   Frontend: implement feature X
   fix for feature backend
   fix for backend API XYZ
   front fix
   backend fix

Yeah again I know I could do better, but yeah I use squashing for this reason. A lot.

[ Parent | on HN ]

Re:Fortunately, I don't squash my commits by Joker_vD on Monday October 05, 2020 @08:45AM (#24687224)

Well, uh, yes, that's what the commit history generally looks like (although we do generally put "JIRA-9999: " in front of all commit messages, for context). So what?

[ Parent | on HN ]

Re:Fortunately, I don't squash my commits by SXX on Monday October 05, 2020 @11:27AM (#24688586)

What I wanted to say that since I don't have that many people other than me looking into my code there no reason to preserve real development history of every feature and IMO 3 "feature commits" are preferable than my development mess of 50 "fix that fix this" commits.

[ Parent | on HN ]