Problem Statement
Ownership Rules currently match against full paths using Unix glob syntax. This works well when stack frame paths are consistent, but it becomes difficult to write maintainable rules when the same logical source file can appear under multiple path prefixes.
As a result, organizations then need to duplicate ownership rules for every possible path variant which can be harder to maintain
Solution Brainstorm
Support more flexible path matching within Ownership Rules, for example:
Matching against a normalized or post-processed path (similar to how CODEOWNERS matching benefits from code mappings)
More expressive matching semantics beyond the current glob-only approach
Related to internal conversation #215474834118900 for reference
Product Area
Settings - Projects
Problem Statement
Ownership Rules currently match against full paths using Unix glob syntax. This works well when stack frame paths are consistent, but it becomes difficult to write maintainable rules when the same logical source file can appear under multiple path prefixes.
As a result, organizations then need to duplicate ownership rules for every possible path variant which can be harder to maintain
Solution Brainstorm
Support more flexible path matching within Ownership Rules, for example:
Matching against a normalized or post-processed path (similar to how CODEOWNERS matching benefits from code mappings)
More expressive matching semantics beyond the current glob-only approach
Related to internal conversation #215474834118900 for reference
Product Area
Settings - Projects