Okay I just get the task of training my colleges to use conventional commits in the future.
Really happy that we start to use that all my learning wasn't wasted for my daily job.

So let's get your commit messages sorted out, yeah.

#GIt #ConventionalCommit #Developer #Programming #VCS

@guerda @cark I've been trying to adhere to conventional commits too and find it quite useful.

I like the convention of including the module/function name in parentheses after the type of commit, e.g. `bug(module1): capture TypeError`

#git #conventionalcommit

Who can help me reduce my dependency on #github? I am looking for (proven) alternatives to PR-based workflows for collaborative development (beyond patches by email). I am particularly concerned about the separation of essential information from the source #Git repo -- for example in PR descriptions/tags from which versions are determined and changelogs are generated.

I am already looking at #radicle, and #ConventionalCommit (via something like https://commitizen-tools.github.io/commitizen).

TIA!

#fedihelp #boost

@BenjaminFaliere

Je pratique le #conventionalCommit depuis une belle lurette, et je recommande.

C'est par ailleurs très pratique pour générer automatiquement des « release notes ».

Neat -- a new #ConventionalCommit versioning policy plugin for newly release #ApacheMaven maven-release-plugin 3.0.0 that just dropped (note the lack of a -M milestone qualifier!!).

https://github.com/nielsbasjes/conventional-commits-maven-release

This looks kinda cool.

Started fiddling with #cocogitto. A cli tool to automate #ConventionalCommit stuff. Absolutely a joy to use.

https://docs.cocogitto.io/