You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/docs/product/issues/ownership-rules/index.mdx
+10-2Lines changed: 10 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -116,8 +116,13 @@ Create external team/user mappings for your GitHub/GitLab teams and users by nav
116
116
If you have both ownership rules and code owners, Sentry evaluates an event’s in-app frames against the rules in the following order:
117
117
118
118
1. Code owners, top-to-bottom
119
+
120
+
a. If there are multiple owners in the rule, left-to-right
121
+
119
122
2. Ownership rules, top-to-bottom
120
123
124
+
a. If there are multiple owners in the rule, left-to-right
125
+
121
126
After evaluation, the last rule matching returns the assignment. The order of the event’s stacktrace filepaths is irrelevant in determining the rule assignment.
122
127
123
128
### Example
@@ -131,15 +136,18 @@ codeowners:*.js #ecosystem
131
136
**Ownership Rules:**
132
137
133
138
```
134
-
path:*.js #ecosystem
139
+
path:*.js #ecosystem #frontend
135
140
path:sentry/api/* #api
136
141
url:*subscription* #billing
137
142
path:dist/frontend/components/* #frontend
138
143
```
139
144
140
145
When Sentry receives an event with a stacktrace filepath: `dist/frontend/components/sidebar.js`, we:
141
146
142
-
1. Evaluate against the code owners top-to-bottom; we get one match.
147
+
1. Evaluate against the code owners top-to-bottom; we get one match with two owners in the rule.
148
+
149
+
a. Evaluate the rule left-to-right; we choose the first owner.
150
+
143
151
2. Evaluate against the ownership rules top-to-bottom; we get two matches.
0 commit comments