Using the commit types
The commit types were part of the previous checklist for best source control practices. We need to elaborate on these commit types as follows, and see how they can help you with each of the preceding scenarios:
- New feature: I found it useful to have a focus factor, and since I am always using a clear list of prioritized features that remain important for the next few days, it was evident that changesets need to relate to that feature. That's why whatever change I do (config file, database, adding a library, changing an application programming interface (API), adding a code file, changing existing code, and so on) needs to be related to the feature I am working on. It's easy for me and my team to grasp changes when it's clear that a commit matches a particular feature as shown here:
commit d6a3b90e95b5e4f356c4236b55707a21465ca67z Author: Adrian Bolboacă <[email protected]> Date: Thu May 28 09:05:15 2020 +0200 New feature...