fix: suggest adding t:none transformation for runtime rules#262
Merged
EsadCetiner merged 1 commit intocoreruleset:mainfrom Jan 25, 2026
Merged
Conversation
airween
approved these changes
Jan 25, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Proposed changes
Adds a suggestion to the false positive tuning docs to always specify the
t:nonetransformation when creating a runtime rule exclusions and updates examples to reflect that. This might be confusing for new users as default transformations may lead to unexpected rule behavior. A reference was also added on the basics of rule creation to ensure the reader is familiar with how a runtime rule works.Further comments
This PR was created based on a discussion in the CRS slack channel where an user was having difficulty in writing an rule exclusion.