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
I'm using this in combination with Azure Devops checks and they report a neutral state back when they are skipped due to path exclusion.
It would be nice if the 'neutral' conclusion state would be marked as success.
There are two ways to do this:
Happy to contribute with a PR.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
I'm using this in combination with Azure Devops checks and they report a neutral state back when they are skipped due to path exclusion.
It would be nice if the 'neutral' conclusion state would be marked as success.
There are two ways to do this:
Happy to contribute with a PR.
The text was updated successfully, but these errors were encountered: