la dernière intervention de @lucsorelgiffo tournait autour des #conventionalcommits (https://youtu.be/KKBBOGeRPJg?si=zejM7RTwFtrQ6PVN&t=578) :
- extension git-commit-plugin + hook de pre-commit commitlint : guider l'écriture du message de commit
- python-semantic-release : calculer la prochaine version du paquet
- le mécanisme de trusted publisher pour pousser le paquet sur PyPI

Conscient des limites de ce formalisme, Luc vous partage cet article très pertinent qui les analyse très bien : https://sumnerevans.com/posts/software-engineering/stop-using-conventional-commits/
#Python #CI

As a companion project to sprig-commit which I published earlier, tonight I created sprig-lint. Similar to #commitlint, it validates the #conventionalCommits format and general styling, but it is implemented as a single #bash 3.2 script with zero dependencies.

https://github.com/nsrosenqvist/sprig-lint

#devtools #git

I created this small #git hook script that helps you work with #ConventionalCommits and issue tagging for commit messages (eg. #Jira). Zero dependencies, pure #bash. I hope it can be useful to someone.

https://github.com/nsrosenqvist/sprig-commit

#devtools

Today I built a script that installs local Git hooks to help maintain Conventional Commits and branch naming conventions. It works globally or per project.

If you’re interested, hit me up :)

#Git #DevOps #Automation #CICD #OpenSource #ConventionalCommits #GitLab

Good commit messages keep the history clean, make it easier to work together and are even machine-readable <3

https://www.conventionalcommits.org/en/v1.0.0/

With this standard, commits can be automatically turned into nice, clear changelogs.

#conventionalcommits

Tác giả đề xuất hệ thống đặt tên commit Git mới, chi tiết hơn Conventional Commits. Nó phân loại rõ ràng thay đổi "Hướng người dùng" (ví dụ: feat, fix) và "Nội bộ" (ví dụ: refactor, chore). Mục tiêu là giúp commit message rõ ràng và dễ hiểu hơn. Bạn nghĩ sao?

#Git #LậpTrình #Commit #ConventionalCommits #PhátTriểnPhầnMềm
#Git #Programming #CommitNaming #SoftwareDevelopment #DevOps

https://www.reddit.com/r/programming/comments/1pui0hc/commit_naming_system/

Just published a guide on using changelogen + a custom AI slash command to auto-generate and clean up your ‎`CHANGELOG.md` from Conventional Commits. Duplicate issues gone, contributor names fixed, semantic bumps handled.

https://flori.dev/reads/changelogen-ai-agent/

#TypeScript #DevTools #ConventionalCommits #changelog

So... I use #gitmoji for my #ConventionalCommits, and I absolutely love it. I've been using semantic-release-gitmoji [1] in order to build a `CHANGELOG.md` file out of the commit history, but it doesn't seem to be particularly well-maintained. I'm currently bumping up against a security vulnerability that I can't patch (reliably) because of a transient dependency, so I'm hoping somebody out there has an alternative approach. A cursory web search turned up bupkis.

I'm not necessarily married to semantic-release, but I like it quite a bit and would prefer to continue using it if possible. (I've used release-please in the past and thought it was decent, as well, so if there's a solution involving that, maybe I'd be up for it.)

Does anybody else build changelogs from conventional commits using gitmoji? If so, what's your stack?

1. https://github.com/momocow/semantic-release-gitmoji