chore: remove dynamic severity entirely #1504
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cfabianski
force-pushed
the
chore/remove-dynamic-severity-for-data-type
branch
from
9f51f5c
to
9fbf424
Compare
cfabianski
force-pushed
the
chore/remove-dynamic-severity-for-data-type
branch
from
be07547
to
f5312da
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Farewell dynamic severity
Bearer/bearer-rules#289
We will create 2 rules, 1 with data_type will have a default severity set to high and 1 without with a low severity.
We don't need this dynamic severity anymore :)
Checklist