Instructions in step 1's readme says Select the checkbox next to Set as a pre-release, since it is representing a beta version.
However, my step 1 workflow did not trigger.
I had to uncheck it to trigger step 1.
Screenshot above shows action history.
Ignoring the last 2, next 3 were from following instructions. Then 1 manual trigger of step 1. Then unchecking to properly trigger workflow 1.
I notice the grey font below changed from published by to Release v0.9 published by. It seems that Set as a pre-release does not count as
release:
types: [published]
How do we know what exactly defines published? Official docs are not helpful in solving this bug and I had to experiment before raising this issue.
Why are all the other failed actions named after the workflow file name name: Step 1, Create a beta release while the successful trigger is named as the release title First beta release? When does actions UI follow workflow file name and when does it show some other text?
Instructions in step 1's readme says
Select the checkbox next to Set as a pre-release, since it is representing a beta version.However, my step 1 workflow did not trigger. I had to uncheck it to trigger step 1.Screenshot above shows action history. Ignoring the last 2, next 3 were from following instructions. Then 1 manual trigger of step 1. Then unchecking to properly trigger workflow 1.
I notice the grey font below changed from
published bytoRelease v0.9 published by. It seems thatSet as a pre-releasedoes not count asHow do we know what exactly defines published? Official docs are not helpful in solving this bug and I had to experiment before raising this issue.
Why are all the other failed actions named after the workflow file name
name: Step 1, Create a beta releasewhile the successful trigger is named as the release titleFirst beta release? When does actions UI follow workflow file name and when does it show some other text?