-
Notifications
You must be signed in to change notification settings - Fork 347
/
CODEOWNERS
Validating CODEOWNERS rules...
53 lines (32 loc) · 1.22 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
42
43
44
45
46
47
48
49
50
51
52
53
* @segmentio/segment-doc-team
# The default owners for everything in
# the repo. Unless a later match takes precedence.
CODEOWNERS @segmentio/segment-doc-team
# Utility scripts
/scripts @segmentio/segment-doc-team
# Vale Linting
# /vale-styles @segmentio/segment-doc-team
# .vale.ini @segmentio/segment-doc-team
# Content owners should be in the order of PM, TL (team-lead), and EM (in a crisis) for a given team.
# This team will receive review requests automatically when a PR is submitted modifying the files in
# a given directory+subtree, or file type, etc. that matches below. While Github won't enforce the
# order names are listed in for the PR review, this file can provide insight on who should be contacted
# if anything becomes time sensitive. Names other than the PM can mostly ignore these review notifications
# but are listed here as backup.
# Libraries owners
/src/connections/catalog/libraries @stayseesong
# Destinations owners
# /src/connections/destinations @stayseesong=
# Stratconn
## Adobe
## Facebook
## Google
## Salesforce
# Engage
/src/engage/ @pwseg
# Unify
/src/unify @pwseg
# Protocols owners
/src/protocols @forstisabella @pwseg
# Storage owners
/src/connections/storage @forstisabella @pwseg