feat: add highest_level= parameter to Actions class
#124
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When defining actions for thresholds, the case may be that:
Having all three actions fire can result in undesired redundancy (i.e., over-signalling failure) and it's likely more often the case you'll want only the action from the most severe threshold that was exceeded.
This PR solves this by adding the
highest_level=parameter toActionsclass. It's set toTrueby default so the less common scenario (the one above) can be accessed withhighest_level=False.Here's an example of its use:
With
highest_only=Falsewe'd get this in the console: