-
Notifications
You must be signed in to change notification settings - Fork 3
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
Will prereleases automatically be released on GitHub as such? #1
Comments
From reading the docs here, it seems I need to specify the tag manually, from the output of the Python Semantic Release action. Is that the case? I'm slightly confused. |
@MicaelJarniac, first I would like to apologize that your issue never got a response when requested, I was not one of the maintainers at that time but I will do my best to answer your question even if you have understandably moved on or figured it out already.
Yes, this action uploads artifacts to an existing release if found. If a release is not found, it will log a warning and end. The prerelease setting itself does not affect the
It is an optional parameter. Our example passes it specifically from the actual PSR action. If you don't provide the tag then it will default to |
This issue has not received a response in 14 days. If no response is received in 7 days, it will be closed. We look forward to hearing from you. |
This issue was closed because no response was received. |
If a release is generated by Python Semantic Release with the
tool.semantic_release.branches.*.prerelease = true
option, will this action upload it to GitHub as a prerelease?The text was updated successfully, but these errors were encountered: