鉂� About
When you create software, delivering it as fast as possible :
- 馃洝锔� Without impacting your end-users with breaking changes and deliver
- 鈿� Consistently deliver features as soon as they are ready
- 馃挕 Deliver on-purpose versions according to a coherent semantic
- 馃摐 Deliver nice looking and auto-documented release notes
馃 You have no option : "you have to automate that"... and the best place to do that is just at the beginning of the pipeline :** within code activity, within the commits themselves.**
馃幆 What you'll learn (< 15')
In this post (and without any git required knowledge), you'll see how this can be achieved within a simple yet very powerful demo that helps understand core concepts.
馃嵖 Demo
馃搼 Resources
- Conventional Commits
semantic-release- Commitizen
IntelliJConventional Commit pluginVS CodeConventional Commits extensionmaven-semantic-releasesemantic-release-helmsemantic-release-pypisemantic-release-gh-pages-plugin@semantic-release/github@semantic-release/release-notes-generator
馃檹 Acknowledgments
kudos to @lschaeffer313 for the session, we had a great moment together... and the technique has been adopted on all our projects, for a daily usage.
Top comments (3)
Not 馃挬, here's how to write actually good commit messages (hint: It's not just adding commit-lint)
Jayant Bhawal for Middleware 銉� Jun 6