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
We should have an agreed upon way to produce a changelog for releases.
Personally, I like the idea of leveraging GitHub Issues, which can generate changelogs based on closed PRs. This way, a well named PR (when it is closed-as-completed) can simply be included in the changelog.
One thing I have my eye on is release-drafter - a GitHub Action that automatically drafts release notes based on commits and pull requests. It can be configured to include specific labels, milestones, and other metadata, which could be useful in tracking work in relation to organizational goals.
When we agree on the method, I can include it in the CONTRIBUTING.md file.
Please enter your opinion in a comment here, or give me a simple thumbs up!
The text was updated successfully, but these errors were encountered:
We should have an agreed upon way to produce a changelog for releases.
Personally, I like the idea of leveraging GitHub Issues, which can generate changelogs based on closed PRs. This way, a well named PR (when it is closed-as-completed) can simply be included in the changelog.
One thing I have my eye on is
release-drafter
- a GitHub Action that automatically drafts release notes based on commits and pull requests. It can be configured to include specific labels, milestones, and other metadata, which could be useful in tracking work in relation to organizational goals.When we agree on the method, I can include it in the CONTRIBUTING.md file.
Please enter your opinion in a comment here, or give me a simple thumbs up!
The text was updated successfully, but these errors were encountered: