Skip to content
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

Implement strict mode #2533

Merged
merged 1 commit into from
Oct 1, 2022
Merged

Implement strict mode #2533

merged 1 commit into from
Oct 1, 2022

Conversation

ssbarnea
Copy link
Member

@ssbarnea ssbarnea commented Oct 1, 2022

From now, you can add --strict to make it return a non zero error
code even if only warnings are found.

Related:

From now, you can add --strict to make it return a non zero error
code even if only warnings are found.

Related:
- ansible#1742
- ansible#2530
@ssbarnea ssbarnea requested a review from a team as a code owner October 1, 2022 19:40
@github-actions github-actions bot added the bug label Oct 1, 2022
@ssbarnea ssbarnea merged commit b4fd3ea into ansible:main Oct 1, 2022
@ssbarnea ssbarnea deleted the fix/strict branch October 1, 2022 20:06
ssbarnea added a commit to ssbarnea/ansible-lint that referenced this pull request Oct 5, 2022
From now, you can add --strict to make it return a non zero error
code even if only warnings are found.

Related:
- ansible#1742
- ansible#2530
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant