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
Each PR that adds/changes/fixes something notable in terms of CHANGELOG, should provide a Markdown file named using PR number (or the issue number) and the category of change in a folder.
For example a file could be created unders draftlogs/5678_fix.md for a bug fix or draftlogs/5678_add.md for a new feature, etc.
Having these files on master at any time one could simply npm run script to draft the next release notes.
Also we could use this script to quickly draft, then finalize the changelog.
This folder could automatically be emptied during the release process to help collect the changes for the next release.
The text was updated successfully, but these errors were encountered:
Each PR that adds/changes/fixes something notable in terms of CHANGELOG, should provide a Markdown file named using PR number (or the issue number) and the category of change in a folder.
For example a file could be created unders
draftlogs/5678_fix.md
for a bug fix ordraftlogs/5678_add.md
for a new feature, etc.Having these files on master at any time one could simply npm run script to draft the next release notes.
Also we could use this script to quickly draft, then finalize the changelog.
This folder could automatically be emptied during the release process to help collect the changes for the next release.
The text was updated successfully, but these errors were encountered: