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
@ibnesayeed has crafted automation of the release and testing process through GitHub actions, inclusive of generating the release notes. These release notes, among other things, contains the Pull Requests since the last release.
However, listing the issues closed would also be informative. @ibnesayeed stated that he is not aware of how to do this using the git log. Is there a way, with GitHub actions, to determine this and use it as a basis for inclusion in release notes?
The text was updated successfully, but these errors were encountered:
Perhaps GitHub's CLI can help here, because issues are not a Git property, but a GitHub overlay. It should be possible to query that information, but we need to identify a reliable means to identifying false positives. If we were using SemVer-style release plan, then we could have added labels to easily filter issues related to a planned release.
This is a meta-ticket.
@ibnesayeed has crafted automation of the release and testing process through GitHub actions, inclusive of generating the release notes. These release notes, among other things, contains the Pull Requests since the last release.
However, listing the issues closed would also be informative. @ibnesayeed stated that he is not aware of how to do this using the git log. Is there a way, with GitHub actions, to determine this and use it as a basis for inclusion in release notes?
The text was updated successfully, but these errors were encountered: