Always use regex matcher when determining contacts for build failure notifications #5487
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.
Follow-up PR:
NotificationConfigurationNuGet package version to1.0.0-dev.20230216.1to enableCODEOWNERSregex matcher everywhere #5488This PR is a follow-up to:
NotificationConfigurationpackage to20230214.1to enableCODEOWNERSregex matcher to default totrue#5452CodeownersFile.UseRegexMatcherDefaulteverywhere where applicable + remove obsolete tests #5437That previous PR was aiming to enable the new regex-based matcher everywhere, but didn't. Now it will, once the NuGet feed is updated. This is because by not passing the
useRegexMatcherargument, I am relying on the default oftrue, set by:CodeownersFile.UseRegexMatcherDefaulteverywhere where applicable + remove obsolete tests #5437Related work: