Fix code owners to capture deep changes and force absolute paths #3363
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.
What does this PR do?
Existing code owners did not work as intended with changes exclusive to deep nested files and may match on unintended files due to lack of absolute path usage (e.g. any nested
ext
dir would be attributed to profiling).Refer to the example to see why the existing rules were wrong:
Motivation:
Proper tagging of relevant reviewers. Here's an example where the existing rules did not target
@Datadog/profiling-rb
but should have: #3352Additional Notes:
How to test the change?
For Datadog employees:
credentials of any kind, I've requested a review from
@DataDog/security-design-and-guidance
.Unsure? Have a question? Request a review!