New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add alternative trigger options #1471
Conversation
These options work the same as the curl command, but use a GitHub App so there's no need to provision and manage a Personal Access Token in order to trigger the Semantic Release action.
The goal of semantic-release is to help releasing any code change as soon as possible, which is why we recommend to run it on each push. |
If it's of any value, I have work projects where we don't release every time we merge because we have specific deploy days. It feels like you lose some of the magic of using semantic-release when every release only has one note in it, versus having many stock piled. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find that quite interesting, I don't mind adding that, some users might find it useful (I could see myself using it in some circumstances), and it's the right place to inform GItHub Actions users about it.
🎉 This PR is included in version 17.0.8 🎉 The release is available on: Your semantic-release bot 📦🚀 |
…se#1471) These options work the same as the curl command, but use a GitHub App so there's no need to provision and manage a Personal Access Token in order to trigger the Semantic Release action.
These options work the same as the curl command, but use a GitHub App so there's no need to provision and manage a Personal Access Token in order to trigger the Semantic Release action.
Full disclosure, I'm personally involved with Actions Panel. Not involved at all with Action Button.