Post B6MRhWnDybTvbS4kV6 by futurile@mastodon.social
 (DIR) More posts by futurile@mastodon.social
 (DIR) Post #B6KauKqqCHq5bQ1s3s by civodul@toot.aquilenet.fr
       0 likes, 0 repeats
       
       TIL that the fashionable “feat”, “fix”, “chore” convention for commit messages is documented:https://www.conventionalcommits.org/en/v1.0.0/Seems to originate from web/JS projects?
       
 (DIR) Post #B6KbSr3axnalKgSH32 by defuneste@fosstodon.org
       0 likes, 0 repeats
       
       @civodul this is what I have as "ref" https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#commit-message-formatso it could be related 🤷‍♂️
       
 (DIR) Post #B6L0Zz9fke1JKTnJuS by isak@social.spejset.org
       0 likes, 0 repeats
       
       @civodul Yea I only found out like yesterday too. I ended up looking it up because so many AI slop projects are filled with commits like that so I thought maybe that's what claude does for a second
       
 (DIR) Post #B6LppTH594HCkWOyTA by civodul@toot.aquilenet.fr
       0 likes, 0 repeats
       
       @isak Heh, I had the same reaction actually and thought it must come from some big company out there.
       
 (DIR) Post #B6MRhWnDybTvbS4kV6 by futurile@mastodon.social
       0 likes, 0 repeats
       
       @civodul One of the things that's nice about 'conventional commits' is there's tooling for creating 'changelog' human-readable things from it. Not sure it would necessarily scale to #guix / distro usage (it would be a big list), but it's quite nice.
       
 (DIR) Post #B6OSXlRV8wJgPdk7Ga by simendsjo@fosstodon.org
       0 likes, 0 repeats
       
       @futurile @civodul guix commit messages really feels like a relic of the past. I would have loved to see commits explaining the why instead of the what. Sure, it's still possible to state before the very detailed list of changes, but people don't do that. And keeping the list of changes makes sense for files not under version control, but why require this when using vcs?
       
 (DIR) Post #B6OSXldYQ7xR11Nk3M by civodul@toot.aquilenet.fr
       0 likes, 0 repeats
       
       @simendsjo One important thing to me is to keep the “why” as comments in the code, when it’s needed.I can relate to the feeling about Guix commit messages, but note that ‘git log’ doesn’t quite give the same information (which definitions where touched, code that was moved, etc.)@futurile