-
Notifications
You must be signed in to change notification settings - Fork 129
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
Regression in latest 1.2.1 version #50
Comments
Hmmm interesting, maybe a good reason it was the way it was before! |
Should be fixed in |
Observing this issue in v1, after the update. |
Still breaking even at |
A workaround for the time being, adding
|
Can confirm, workaround works. Going to leave this pinned to a git sha ;)
|
It doesn't work if I use a |
Realize there was a release tagging issue |
Cheers, it looks like it's working for me now, thanks. |
Closing for now as it seems to be fixed |
Bug description
We see strange behavior in our workflows, after upgrading to the latest 1.2.1 version.
After this change, now if the passed
ref
is an empty string, the action is not calculating the ref and the step fails.Example:
In the case when a
workflow_dispatch
event triggers this workflow, thegithub.head_ref
is empty, but now the action doesn't calculate thegithub.ref
, as aref
input is passed, so the ref ends up as an empty string and the workflow execution fails with:The text was updated successfully, but these errors were encountered: