-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Expand file tree
/
Copy pathTEAMS.yaml
More file actions
91 lines (90 loc) · 2.61 KB
/
TEAMS.yaml
File metadata and controls
91 lines (90 loc) · 2.61 KB
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
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
# This is a YAML file mapping team aliases from GitHub to
# metadata about the team.
# Expected structure is available in pkg/internal/team/team.go.
cockroachdb/docs:
aliases:
cockroachdb/docs-infra-prs: other
cockroachdb/sql-foundations:
aliases:
cockroachdb/sql-api-prs: other
label: T-sql-foundations
cockroachdb/sqlproxy-prs:
label: T-cloud-platform
cockroachdb/sql-queries:
aliases:
cockroachdb/sql-queries-prs: other
cockroachdb/sql-optimizer: other
cockroachdb/sql-opt-prs: other
# SQL Queries team uses GH projects v2.
# See .github/workflows/add-issues-to-project.yml.
label: T-sql-queries
silence_mentions: true
cockroachdb/kv:
aliases:
cockroachdb/kv-triage: roachtest
# This is a hack - we can't have the same key twice,
# but it also doesn't seem worth rewriting the aliases
# into slice form for just this.
'cockroachdb/kv-triage ': unittest
cockroachdb/kv-prs: other
cockroachdb/kv-distribution: other
label: T-kv
cockroachdb/admission-control:
label: T-kv,A-admission-control
cockroachdb/spatial:
label: T-spatial
cockroachdb/dev-inf:
label: T-dev-inf
cockroachdb/drp-eng:
label: T-drpeng
cockroachdb/multiregion:
label: T-multiregion
cockroachdb/storage:
label: T-storage
cockroachdb/test-eng:
label: T-testeng
cockroachdb/test-eng-prs:
label: T-testeng
cockroachdb/security-engineering:
label: T-security-engineering
cockroachdb/product-security:
label: T-product-security
cockroachdb/disaster-recovery:
label: T-disaster-recovery
cockroachdb/cdc:
aliases:
cockroachdb/cdc-prs: other
# CDC team uses GH projects v2, which doesn't have a REST API, so no triage column ID
# see .github/workflows/add-issues-to-project.yml
label: T-cdc
cockroachdb/server:
aliases:
cockroachdb/cli-prs: other
cockroachdb/server-prs: other
label: T-db-server
cockroachdb/obs-prs:
# The observability team uses Jira for managing issues. So there is no triage column ID.
label: T-observability
cockroachdb/obs-india-prs:
cockroachdb/jobs:
aliases:
cockroachdb/jobs-prs: other
# Jobs uses GH projects v2, which doesn't have a REST API, so no triage column ID
# see .github/workflows/add-issues-to-project.yml
label: T-jobs
cockroachdb/cloud-identity:
cockroachdb/code-systems-prs:
label: T-code-sys
cockroachdb/unowned:
aliases:
cockroachdb/rfc-prs: other
cockroachdb/migrations:
label: T-migrations
cockroachdb/release-eng:
aliases:
cockroachdb/release-eng-prs: other
cockroachdb/upgrade-prs: other
label: T-release
cockroachdb/field-engineering:
# Field Eng isn't currently using github projects.
label: T-field-eng