Workflow fails because of the release name? #369
justalemon
started this conversation in
General
Replies: 1 comment 1 reply
-
You need to either manually set the tag or trigger your workflow from something like a tag push. This will try and use the ref GitHub associated with the workflow but I have no idea what that will be when release creation is the trigger. Further, trigging this action which creates a release from release creation seems like it could cause some weird issues generally. Usually you would trigger you workflow from a tag push, which then creates a release, uploads assets, etc. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm having quite of a weird behavior here, and I ain't sure if is a bug or I missed something.
I have this workflow file that triggers when I create a release, and it causes some weird behavior depending on what I name the release.
Is that normal? I would expect it to take the name from the release payload data so it should have the tag.
Beta Was this translation helpful? Give feedback.
All reactions