I found the conventional commits description under “Thea’s Pantry Workflow” interesting. This is new to me, but I see the importance of being able to control all developers to use the same formula in describing commits. It is also necessary to use the semantic versioning [1] to not only be an asset to developers and managers following other developer’s work in a controlled manner, but allowing the connection of the GitLab commits to be integrated with testing, and deployment in an automated fashion (CI/CD)

[1]  FIX/PATCH  – generally bug fixes

      FEAT/MINOR – a full new feature that does not break the code-base,

      BREAKING CHANGE/MAJOR.

I am also interested in learning Kubernetes, as well as understanding better how continuous integration and deployment will be used in our product.

From the blog cs@worcester – (Twinstar Blogland) by Joe Barry and used with permission of the author. All other rights reserved by the author.