-
Notifications
You must be signed in to change notification settings - Fork 32
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
allow_failure
is poorly named
#7
Comments
Agreed, it's quite confusing. I had to run a few tries until I figured out what's happening. I wouldn't change the name without a major version bump, but the correct explanation in the Readme would help. In either check, the "file exists" step doesn't run if the files don't exist. |
Oh - I suddenly got it. "allow_failure" means of the overall ACTION not of the check for files ... otherwise, any files that don't exist stop the action. That's sort of what you want, but usually steps fail anyway if there's a missing file. Still, this desperately needs clarification |
Whilst it's not a game changer - this could be good to rename in the next version? I think the description you've got is perfect but 🤯 took me a while
|
Hi! I have finally changed the Hopefully, this will avoid any future confusion (and frustration) 😅 |
I would expect if
allow_failure
is false... it would not be allowed to fail finding the files. This is currently not the case... ifallow_failure
is false, the step will succeed if the files are not found.Alternatively if I set
allow_failure
to true... it fails the step if the files don't exist. That's not allowing a failure.The text was updated successfully, but these errors were encountered: