News for hackers. Stuff that matters.

A comment on Comparing Git Workflows. Parent comment

Re:Comparing Git Workflows by cortesoft on Thursday May 26, 2016 @08:22PM (#11782923)
I commit for lots of reasons, though. Sometimes, I am about to try something crazy with the code, and I want a save point to go back to. Sometimes, I want to switch computers in the middle of working on something (going from desktop to laptop, for example), so I commit and push to the other computer.

Also, if I am working on something very complex, I might go hours or even days with code that can't compile. I don't want to risk losing that because I was avoiding committing.

A lot of these problems can be resolved with the proper use of --fixup and --squash and auto squash rebasing.

[ Parent | on HN ]
Re:Comparing Git Workflows by mikegerwitz on Friday May 27, 2016 @09:04AM (#11785697)
My argument was for not retaining those commits, or not committing them in the first place; drewg123 was complaining about the situation from others, meaning that their private branches were not cleaned up prior to pushing. You wouldn't push your WIP branch, I would assume.

I have also pushed for the purpose of pulling on another PC; that commit then gets `reset --soft`'d.

[ Parent | on HN ]
Re:Comparing Git Workflows by cortesoft on Friday May 27, 2016 @11:44AM (#11786738)
I usually want to push it somewhere, to maintain a backup in case of hardware failure.
[ Parent | on HN ]