Before I start the question I want to tell you guys I'm new to this type of workflow. The previous companies I worked didn't used Version Control and/or changelogs. Also, I've been working as freelancer for sometime, so never felt the necessity to do so. But now I'm trying to have a better organization of my projects and I'm trying to use changelogs and Version control.
I was also reading other questions here and I understood the purpose of a version control, changelog, semantic version (which is the version type I'll be using), currently I'm using SourceTree (locally), I also understood the concept for each commit, branch, etc...
What I don't understand very well is how to integrate the Version control (commits) with a detailed changelog. What should go into the changelog? How often should I update it? How should it be segmented?
For example, if I'll update the changelog for each commit, it can be very extensive, but it's also important to have detailed information about the progress on the project.
Since the third number is related to bug fixes, instead of features, should I segment the changelog based on the feature version number? For example:
# 1.2.0 - Description of this version. - Fixes + 1.2.1 - This is the fix number 01 + 1.2.2 - This is the fix number 02 + 1.2.3 - This is the fix number 03 + 1.2.4 - This is the fix number 04 # 1.1.0 - Description of this version. - Fixes + 1.1.1 - This is the fix number 01 + 1.1.2 - This is the fix number 02 + 1.1.3 - This is the fix number 03 + 1.1.4 - This is the fix number 04
Or what other considerations do i need to have when adopting this type of workflow? Keep in mind I'm new to this scenario, so every type of information for me would be very appreciated!