We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Why would I want pipefail to be set when:
A) the command can't fail because I said so B) the failure condition is nontrivial, such as "the error message does not contain Y word"
?
Example code that E306 shouldn't warn about:
- shell: "pgrep stuff | wc -l" # noqa 306 failed_when: false changed_when: false check_mode: false register: stuff_is_running
The text was updated successfully, but these errors were encountered:
I guess that the presence of failed_when: false should disable this rule. Feel free to make a PR to add this, it does make sense.
failed_when: false
Sorry, something went wrong.
Improve risky-shell-pipe rule matching
972c701
Removes one false positive case where user set ignore_errors: true, case in which the rule does not make much sense. Fixes: #1250
Improve risky-shell-pipe rule matching (#1453)
1be1871
Successfully merging a pull request may close this issue.
Why would I want pipefail to be set when:
A) the command can't fail because I said so
B) the failure condition is nontrivial, such as "the error message does not contain Y word"
?
Example code that E306 shouldn't warn about:
The text was updated successfully, but these errors were encountered: