Allow case-insensitive matcher in rules.exists and rules.changes
Problem to solve
We do not currently provide a way to perform a case-insensitive match using
rules.exists, we should consider providing either providing a case-insensitive matcher, support for regexes, or consider making the default
rules.exists match case insensitive.
User experience goal
Easier matching using
- Provide regex support within
- Introduce new matcher syntax
This issue was born out of #220983 where is running into the upper limit for matchers. We have a large enough glob list where we run into issues during global project path matching.
Permissions and Security
No change to permissions
Availability & Testing
What does success look like, and how can we measure that?
rules.changes support for case-insensitivity
What is the type of buyer?
Is this a cross-stage feature?