-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Enhancement: A flag for providing inputs #1021
Comments
I second this. It would be super useful. |
@catthehacker @KnisterPeter 🔝 what do you think? I'm using this library for the first time and this is the first thing I noticed is missing. Thanks! |
@Yago-Ferrer feel free to start implementing and contributing it |
If issue is not closed, it's free to implement. If it's not implemented yet, it's most likely up to you to do it (until we fix all the major issues and problems with higher priority :). |
It would be great if act aligned with github's workflow command in |
I would like to take this issue if no one is working on it |
Would be great if I could say
--input name=value
instead of having to create a file as per #332.I am using GitHub Actions for tasks like "deploy a certain branch to staging", etc, and nearly all my actions currently require inputs. (While, on the other hand, I don't have any
on: push
actions.)The text was updated successfully, but these errors were encountered: