But then this week I spend three days cleaning things
up. That's no good, man. What for? Nobody is watching my repository.
git checkout feature-branch
git rebase master
git rebase -i HEAD~4
git rebase -i HEAD~4
Pretty much all my life I've been working alone [1].
Working alone it matters little whether I commit often or not.
It turns out I don't like to commit just because I wrote some new
function.
I don't think git should be used as some kind of backup system,
although it is.
I like a history that's organized. As a result, I sometimes rewrite
history to fix some of these mistakes I make.
I know enough about it to really clean things up and rewrite the history---it's okay because I'm working alone.
It's only a "backup" in the sense of "this didn't work, I need to go
back to something that does".
turns out I don't like to commit just because I wrote some new
function.
On Tue, 10 Nov 2026 18:26:19 -0300, Anton Antimo wrote:
Pretty much all my life I've been working alone [1].
So do I.
Working alone it matters little whether I commit often or not.
I commit when it makes sense, not when it doesnrCOt.
It turns out I don't like to commit just because I wrote some new
function.
Commits should consist of a group of changes that make some kind of
cohesive sense.
On 2026-11-11, Lawrence DrCOOliveiro wrote:
Commits should consist of a group of changes that make some kind of
cohesive sense.
I find it helpful too for "I'm not sure this is going to work" type
changes, in the sense of "no, that didn't work, go back...".
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 53:29:03 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,430 |