3 ms·
as a solo developer, you are free to commit however you want I use commits as rollback points. If something works and I want to try something risky, I commit f
by hsn915 3y ago
as a solo developer, you are free to commit however you want
I use commits as rollback points. If something works and I want to try something risky, I commit first. I don't care about the commit message. I basically never look at any commit older than one month
- olavfosse 3y ago$ git commit --allow-empty -m ''
- hsn915 3y agoThat's not what it means to not care about commit messages. It means the commit only needs to make sense to my self until next week. If I see a commit from 2 weeks ago and I don't know what the message means, who cares? I hardly look at those commits.
- wvenable 3y agoI do the same. I also commit at logical completion points that build cleanly. I hardly ever look at commits older than the last commit. I don't often create branches for features; I find having permanent Production / Test / Dev branches is sufficient for most work. But I will create other branches as needed. Git worktree is awesome for having multiple branches checked out all at the same time. At this point, I almost never switch branches and instead check them out into their own directory.
- thesnide 3y agosame here. i even commit automatically before every compilation. that's why i created https://github.com/steveschnepp/git-breadcrumb https://github.com/steveschnepp/git-breadcrumb A little rough but works well enough for my current workloads.
- erik_seaberg 3y agoIf I can’t remember the reason for a piece of code, and it wasn’t obscure enough to comment, I need to use “git blame” and then look at the message from the commit.