Automatically generated changelogs can only be kept sane if commits are isolated to a single module. For example, changing stately-react may require upstream changes in stately-async, but the commit message for stately-async needs to be independently clear; that is, it should only reference API changes or additions that are relevant to its own code.
To achieve this, changes that span multiple modules need to be split into separate commits - one per module. Commits that span multiple modules should be rejected, forcing the developer to create a separate commit for each module change.
hiebj
commented
6 years ago
Automatically generated changelogs can only be kept sane if commits are isolated to a single module. For example, changing
stately-reactmay require upstream changes instately-async, but the commit message forstately-asyncneeds to be independently clear; that is, it should only reference API changes or additions that are relevant to its own code.To achieve this, changes that span multiple modules need to be split into separate commits - one per module. Commits that span multiple modules should be rejected, forcing the developer to create a separate commit for each module change.