Ownership Rules: Request for more flexible path matching
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating Ownership Rules' current Unix glob matching and the path processing used for stack frames, then review how CODEOWNERS code mappings handle path variants. Done requires agreed matching semantics, implementation coverage, and tests for multiple path prefixes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100