-
Notifications
You must be signed in to change notification settings - Fork 102
/
CODEOWNERS
Validating CODEOWNERS rules...
41 lines (28 loc) · 1.07 KB
/
CODEOWNERS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
# Teams can be specified as code owners as well. Teams should
# be identified in the format @org/team-name. Teams must have
# explicit write access to the repository.
# More details are here: https://help.github.com/articles/about-codeowners/
# The '*' pattern is global owners.
# Order is important. The last matching pattern has the most precedence.
# In each subsection folders are ordered first by depth, then alphabetically.
# This should make it easy to add new rules without breaking existing ones.
# The folders are ordered as follows:
# Dev/API:
/docs/dev/api/error-reporting/ @rick-bt @peter-shao
/docs/dev/api/rdc/ @kristofmuhi
/docs/dev/api/storage/ @kristofmuhi
# Dev:
/docs/dev/cli/ @saucelabs/devx
# Backtrace/Error Reporting
/docs/error-reporting/ @rick-bt @peter-shao
# Sauce Orchestrate
/docs/orchestrate/ @saucelabs/sauce-orchestrate-team
/docs/orchestrate.md @saucelabs/sauce-orchestrate-team
# Mobile apps:
/docs/mobile-apps/ @kristofmuhi
# Web apps:
/docs/web-apps/ @saucelabs/devx
# Dockerfile:
Dockerfile @alexplischke @dpgraham
# Frontend
/src @discombobulateme