In the previous article of this series, we saw how to set up a version control system git. In this article, we will enhance it a bit more.
While we are now able to record the changes of our app development, a few more enhancements will help us with
- Providing some structure to our work
- Ability to communicate our work
Conventional commit is one such tool that helps us to achieve the above. In conventional commit, we compose the git commit message in a specific format.
<type>[optional scope]: <description>
[optional body]
[optional footer]Ref: https://www.conventionalcommits.org/en/v1.0.0-beta.4/#summary
Some example commits with this format are
feat: login with email, passwordISSUES CLOSED: https://agenthunt.atlassian.net/browse/MB-1feat: signup with emailISSUES CLOSED: https://agenthunt.atlassian.net/browse/MB-2docs: add contribution guidelines documentationISSUES CLOSED: https://agenthunt.atlassian.net/browse/MB-6
There are derived benefits of following this structure. Conventional commit ties nicely to a versioning system called SemVer.
SemVer is primarily used for APIs and many might argue that it doesn't make sense for apps (An earlier version of…
