Fix GitLab codeowners exclusion handling - #12021
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit into
Conversation
|
🎯 Code Coverage (details) 🔗 Commit SHA: 965481a | Docs | Datadog PR Page | Give us feedback! |
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
There was a problem hiding this comment.
More details
The PR correctly fixes GitLab CODEOWNERS exclusion parsing by moving exclusions from inverse-matcher logic to section-scoped suppression. Exclusions now properly prevent ownership from their section while allowing other sections to claim the same path, matching GitLab semantics. The implementation separates exclusions into a dedicated collection, checks them before ownership entries, and prevents exclusions from inheriting section defaults — all correct. No regressions or edge cases identified.
📊 Validated against 6 scenarios · Open Bits AI session
🤖 Datadog Autotest · Commit 965481a · What is Autotest? · Any feedback? Reach out in #autotest
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
c341840
into
master
What Does This Do
Fix GitLab CODEOWNERS exclusion parsing. Exclusion patterns now suppress ownership only within their section and do not inherit default owners.
Motivation
GitLab patterns such as
!generate/were treated as inverse matchers. This assigned owners to unrelated paths and failed to exclude matching paths.Additional Notes
test-environment-trigger: skip
Contributor Checklist
type:and (comp:orinst:) labels in addition to any other useful labelsclose,fix, or any linking keywords when referencing an issueUse
solvesinstead, and assign the PR milestone to the issueJira ticket: [PROJ-IDENT]