-
Notifications
You must be signed in to change notification settings - Fork 43
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
Noisy POSIX warning #32
Comments
Hi, I have exactly the same issue. Could we introduce flag to suppress such warnings? |
Will be fixed with release 2.1.0 (coming soon, today or tomorrow). |
@sharat87 you need to set |
Hey @abhilash1in, thanks for sharing that. But wouldn't that hide all POSIX warnings? Is it possible to just hide this one particular warning? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, i'm getting a lot of warnings from your action like "One of the secrets has a name that is not POSIX compliant...", because basically all my secrets are not POSIX compliant. But since the conversion behavior is already documented in the readme and works fine i think it would be ok to use a debug message instead of a warning, this way it can still help to analyze and track down issues but doesn't clutter the workflow logs.
The text was updated successfully, but these errors were encountered: