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
It is often times unclear if a feature is released (or not released yet). Other projects (example: Electron) have extended automation around what is included in a release (and what not).
Given that we already use conventional commits and #closes hints in our commit logs I'm looking towards something similar, i.e. on release:
note which (linked) issue it fixed on the issue
note which (linked) pull request it incorporates, on the PR
Why should we do it?
This improves our communication around releases which would otherwise be manual (i.e. a contributor files a PR and for good measure we need to communicate for them when that gets released).
The text was updated successfully, but these errors were encountered:
What should we do?
It is often times unclear if a feature is released (or not released yet). Other projects (example: Electron) have extended automation around what is included in a release (and what not).
Given that we already use conventional commits and #closes hints in our commit logs I'm looking towards something similar, i.e. on release:
Why should we do it?
This improves our communication around releases which would otherwise be manual (i.e. a contributor files a PR and for good measure we need to communicate for them when that gets released).
The text was updated successfully, but these errors were encountered: