Unwanted warning for undefined input variable in action.yml

Customer developed an action with dynamic inputs, when specify inputs which not mentioned in action.yml, warning will show on logs:

##[warning]Unexpected input 'service', valid inputs are ['file']

Is there a way to avoid this warning? The issue is also happened in octokit/request-action .

There is the ticket in community forum.

[charles-allen]

We add the warning to help the customer better debug their workflow runs like you have a typo

This is a great idea in principle, but I only need to fix a typo once. A permanent YELLOW build is a terrible trade-off for a minor one-time issue.

Accurate real-time status is literally the only job of CI – what’s the point of CI if it always shows “broken”? Please add warning suppression to GitHub Actions

Ideas:

• Add a job property that takes a boolean: suppress-warnings: true
• Add a job property that takes a regex pattern suppress-warnings: 'Unexpected input(s)*'

[gr2m]

@TingluoHuang I have two actions in particular that depend on undefined inputs:

1. https://github.com/octokit/request-action/
2. https://github.com/octokit/graphql-action/

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?