Skip to content

feat: allow neutral conditions #445

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

lazytesting
Copy link

allow neutral condition, this is how Azure Devops checks are reported when the files changed don't match the path filter in the trigger configuration

@userlerueda
Copy link

Is it possible for someone to review this PR? I am using this in our code and CodeQL which come back neutral are not working.
It would even be better if this is a setting that can be passed along in the with:

@cam-bond
Copy link

@dghubble Can you take a look at merging this?

@cmuller-bunnings
Copy link

Is it possible to get this PR merged, please?

@juan-vg
Copy link

juan-vg commented Jul 15, 2025

@lazytesting it could also be useful to provide a new input to specify which statuses should be treated as success (default to current if not provided). In this way, neutral could be treated as success (or skipped could be treated as failure) if needed.

@dghubble this topic looks interesting and your attention here would be so much appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants