@cstanhope Git doesn't strictly require branches, but it's rare to create commits on top of a detached head. I also believe there's no way to push commits that aren't associated with a branch or tag.
Related Posts
It feels like a mature software project is one where bugs require multiple commits to fix.
You've hammered out the basic issues, so the remaining issues are often weird interactions between components.
I'm experimenting with jj this weekend. It seems pretty nice so far, but the mental model is pretty different from git.
For example, there's no `checkout` command. You do `jj new ABC` to switch to a commit, which creates a new empty commit on top of ABC.
I've dabbled with 'conventional commits' for a personal project but I found they slowed me down.
It's not always easy to categorise a commit as a fix, a chore etc. Sometimes refactorings also fix bugs.
Do you use them? I can imagine a large, mature project benefitting more.