3 ms·
The Tweet is kinda hyperbolic. Commit messages are pointless for him in his current context. “ This is a new revelation for me on indie projects not for teams.
by travisjungroth 4y ago
The Tweet is kinda hyperbolic. Commit messages are pointless for him in his current context. “ This is a new revelation for me on indie projects not for teams...”
Which I kinda agree with. The attention that commit messages deserve is highly variable. I’ve been meaning to write a script that will generate a commit message based on the files changed. “added models.py, edited settings.py”. This so I can just blast commits locally but still have some info in the message. When I merge, I squash and make one good message.
(If I really get nerdsniped, I’ll have the message based on the code. Like “edited User.login()”)
- WorldMaker 4y agoI automated a single kind of commit message, which I call "wrench commits" where all I'm doing is running some other tool (package manager, scaffolder, formatter, linter, etc) and committing its changes. These commits I label with a wrench emoji followed by the command line string that was run. I don't typically squash these commits, but if I do need to dig deeper that --first-parent in git blame or git bisect it is easy enough to build an ignorerevs file including all the "wrenchs". Sometimes that history has been specifically useful in frameworks that are very scaffolder/package management heavy with infrequent updates that touch a lot of scaffolding and package. It can be handy to glance at the last big update PR for a partial script list reminder.
- u801e 4y ago> I’ve been meaning to write a script that will generate a commit message based on the files changed. “added models.py, edited settings.py” You can get that information with the git log --name-status parameter.
- travisjungroth 4y agoAwesome, thank you.