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
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
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.
that's why i created https://github.com/steveschnepp/git-breadcrumb
A little rough but works well enough for my current workloads.
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.