-
Notifications
You must be signed in to change notification settings - Fork 951
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
Unwanted warning for undefined input variable in action.yml #514
Comments
#506 This PR is related. |
My PR #506 will at least reduce the number of warnings from 1 per input, per action to 1 per action. My workflow summaries are now just noise and worthless because I have dozens of the same |
@nick-invision thanks for your feedback and contribution, I have merged your PR and will include in the next runner release. We add the warning to help the customer better debug their workflow runs like you have a typo when providing inputs in the workflow YAML file. |
@TingluoHuang I have two actions in particular that depend on undefined inputs: There is no way I can define all possible inputs. Several users complained about the warnings. Could you please add an option that allows me to explicitly allow undefined inputs? |
It confuses my developers |
It would be great if there was a way to suppress this warning. This was the original behaviour when I created my action, but changed after #429 was merged. I now have an open issue allenevans/set-env#7 that I cannot resolve since the input parameters cannot be known ahead of time in |
This is a great idea in principle, but I only need to fix a typo once. Accurate real-time status is literally the only job of CI -- what's the point of CI if it always shows "broken"? Ideas:
|
Customer developed an action with dynamic inputs, when specify inputs which not mentioned in action.yml, warning will show on logs:
Is there a way to avoid this warning? The issue is also happened in octokit/request-action .
There is the ticket in community forum.
The text was updated successfully, but these errors were encountered: