3 ms·
> I was constantly surprised by how many questions I got about something as seemingly simple as the conventional commit format from a crowd of enginerds. I'm n
by irrational 5y ago
> I was constantly surprised by how many questions I got about something as seemingly simple as the conventional commit format from a crowd of enginerds.
I'm not. Writing code and writing git commit messages take entirely different types of thinking. With code you are having to think logically and problem solve to tell the computer what to do. Git messages are more analogous to writing a term paper (though shorter). You have to think about the what you are trying to communicate, how best to describe what this commit is all about, maybe trying to figure out if this counts as a fix or something else, etc. Writing code is fairly easy for me. Writing git commit messages is extremely difficult for me. I sometimes go days without commiting because I'm dreading having to write a commit message.
- rorytbyrne 5y agoI also have this problem, so I made a tool that lets you write your commit messages in-advance. It helps me to focus on one problem at a time. https://github.com/synek/git-plan https://github.com/synek/git-plan One feature I wanted to add was for it to parse your source code for comments with a specific format (e.g. `# git-plan feat xyz` or `# git-plan fix xyz`) and then stitch all the hunks together into commits for you. So all you'd have to do is comment your code and then run `git plan commit` and it would generate commits for you to confirm with y/n. I built a prototype of that here: https://github.com/synek/codeline https://github.com/synek/codeline I haven't worked these for a while unfortunately :(