📜 Better collab flows w. (git) Conventional Commits

❔ 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
• IntelliJ Conventional Commit plugin
• VS Code Conventional Commits extension
• maven-semantic-release
• semantic-release-helm
• semantic-release-pypi
• semantic-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.

Comments

[adriens]

Not 💩, here's how to write actually good commit messages (hint: It's not just adding commit-lint)

Jayant Bhawal for Middleware ・ Jun 6

#programming #git #codereview #productivity

[adriens]

[adriens]

Adrien SALES

@rastadidi

🙋 Wanting to get the shortest #timetomarket , be able to release a feature (or a #bugfix 😅) as soon as it's ready ❔... but without sacrifcing documentation nor #softwarequality 🤔
📝 This short post is for you 👇
dev.to/optnc/better-c…
#continuousintegration

23:15 PM - 08 Feb 2023