News for hackers. Stuff that matters.

A comment on Squash your commits. Parent comment

Re:Squash your commits by itaysk on Saturday April 02, 2016 @03:42AM (#11410654)
Regarding your example - why would you commit any of the 5 little commits, If they didn't complete the task, and also are breaking the product? wouldn't it be better to commit only when you completed the task you were working on? (I mean, if the task is made out of sub-tasks, then I would also commit each subtask or milestone that I feel is important, but this is not the case here)
[ Parent | on HN ]
Re:Squash your commits by Piskvorrr on Saturday April 02, 2016 @03:56AM (#11410686)
Sometimes, having a snapshot is useful even if it's not a snapshot of a completely functional system. "Hmm, this doesn't seem to be a workable approach here; let's commit, checkout an earlier version and branch off that." It's not necessary to push all these experiments (or even keep them in the end), but it might be useful to have them, at least for the moment.
[ Parent | on HN ]
Re:Squash your commits by ghostwriter on Saturday April 02, 2016 @04:15AM (#11410717)
That's what "git stash" is for.
[ Parent | on HN ]
Re:Squash your commits by Piskvorrr on Monday April 04, 2016 @03:33AM (#11420049)
Stash is supported as a first-class citizen by exactly zero tools that I've seen - even though a stash is a commit in all but name ;)
[ Parent | on HN ]