You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After building the initial changelogs for the single packages in my monorepo, I notice that the arrangement of the group headings is sorted alphabetically. The repo has not enabled Linear History and I used Merge for my PR's.
When looking at the most changelogs using Conventional Commit format, Features is the most top heading. I wonder if there is a convention for the heading order, or if it has something todo with the repo setup, or commit order, since when looking at your changelog, it has the right order.
The text was updated successfully, but these errors were encountered:
Hey it's me again 😁
After building the initial changelogs for the single packages in my monorepo, I notice that the arrangement of the group headings is sorted alphabetically. The repo has not enabled
Linear History
and I usedMerge
for my PR's.I have not found any specification related Conventional Commit Changelog heading order, but this issue conventional-changelog/conventional-changelog-config-spec/issues/36, but I also do not know which
changelog conventions
your generator follows.When looking at the most changelogs using Conventional Commit format,
Features
is the most top heading. I wonder if there is a convention for the heading order, or if it has something todo with the repo setup, or commit order, since when looking at your changelog, it has the right order.The text was updated successfully, but these errors were encountered: