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
{{ message }}
This repository has been archived by the owner on May 5, 2024. It is now read-only.
First, I'd like to thank you for the great work and functionality provided by this action.
I'd like to use this action within a workflow where I first generate the semver tag using other means, then use this action to create the release and upload the assets.
With that in mind, I was wondering if it would be possible to pass the newly generated tag name in the automatic_release_tag arg and still have your action generate the changelog with all commits since the previous semver compatible tag.
Currently, if the automatic_release_tag is provided, the action does not search for the previous semver compatible tag, therefore no commits are found and no changelog is generated.
Thanks!
The text was updated successfully, but these errors were encountered:
First, I'd like to thank you for the great work and functionality provided by this action.
I'd like to use this action within a workflow where I first generate the semver tag using other means, then use this action to create the release and upload the assets.
With that in mind, I was wondering if it would be possible to pass the newly generated tag name in the automatic_release_tag arg and still have your action generate the changelog with all commits since the previous semver compatible tag.
Currently, if the automatic_release_tag is provided, the action does not search for the previous semver compatible tag, therefore no commits are found and no changelog is generated.
Thanks!
The text was updated successfully, but these errors were encountered: