3 ms·
Raise your hand if commits are mainly just a way to save progress. It can’t just be me. I appreciate that needs differ between projects. In some public project
by Waterluvian 4y ago
Raise your hand if commits are mainly just a way to save progress. It can’t just be me.
I appreciate that needs differ between projects. In some public project I’d be more disciplined. But at work I just commit like a madman and collapse them all automatically upon merge.
- ISL 4y agoThe key world is "mainly". If things go wrong, you haven't just saved progress, but also saved history. That distinction is powerful.
- Waterluvian 4y agoIndeed. A clean history can be helpful. And this is certainly context specific. In my experience it hasn’t been as useful as the cost to do so, so I’ve relaxed a bit on making my commits carefully.
- deleted 4y ago[deleted]
- harryvederci 4y agoFor work it's different, but for my side project: $ git log --pretty=oneline | wc -l # Total amount of commits. 1369 $ git log | grep '^ \.$' | wc -l # Count commits with a message of "." 902
- deleted 4y ago[deleted]
- tkiolp4 4y agoHere. I have a colleague obsessed with the “perfect” commit, with rebase instead of fast forward merges and what not. Can’t stand it. I do care about writing a good summary commit title that includes the Jira issue number that links to a well description of the feature/issue at hand.
- cratermoon 4y agoDo you also push to the central repo, on your branch? Or wait until you're at a reasonable "checkpoint" to push?