/
TEAMS.yaml
109 lines (107 loc) · 3.38 KB
/
TEAMS.yaml
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
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
# 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.
# Finding triage_column_id:
# TriageColumnID is the column id of the project column the team uses to
# triage issues. To get it, open the project, click the "..." on top of
# the project column, and click "Copy column link". That link contains
# the ID as the `#column-<ID>` fragment.
#
# You can also use:
# https://github.com/cockroachlabs/github-find-triage-column-id using
# `go install github.com/cockroachlabs/github-find-triage-column-id@latest`.
#
# Then to retrieve triage_column_id from a repo-based project, run:
# github-get-column-id --repo "cockroach" --project "Bazel" --column "To do"
# Or retrieve the triage_column_id from a organization-based project, run:
# github-get-column-id --project "Spatial" --column "Backlog"
cockroachdb/docs:
triage_column_id: 3971225
aliases:
cockroachdb/docs-infra-prs: other
cockroachdb/sql-foundations:
aliases:
cockroachdb/sql-syntax-prs: other
cockroachdb/sqlproxy-prs: other
cockroachdb/sql-api-prs: other
triage_column_id: 19467489
label: T-sql-foundations
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, which doesn't have a REST API, so
# there is no triage column ID.
# See .github/workflows/add-issues-to-project.yml.
label: T-sql-queries
silence_mentions: true
cockroachdb/kv:
aliases:
cockroachdb/kv-triage: roachtest
cockroachdb/kv-prs: other
triage_column_id: 14242655
label: T-kv
cockroachdb/replication:
aliases:
cockroachdb/repl-prs: other
label: T-kv-replication
cockroachdb/spatial:
triage_column_id: 9487269
label: T-spatial
cockroachdb/dev-inf:
triage_column_id: 10210759
label: T-dev-inf
cockroachdb/multiregion:
triage_column_id: 11926170
label: T-multiregion
cockroachdb/storage:
aliases:
cockroachdb/admission-control: other
triage_column_id: 6668367
label: T-storage
cockroachdb/test-eng:
triage_column_id: 14041337
label: T-testeng
cockroachdb/test-eng-prs:
triage_column_id: 14041337
label: T-testeng
cockroachdb/security:
label: T-cross-product-security
cockroachdb/prodsec:
label: T-cross-product-security
cockroachdb/disaster-recovery:
triage_column_id: 3097123
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
triage_column_id: 2521812
cockroachdb/obs-prs:
# The observability team uses Jira for managing issues. So there is no triage column ID.
label: T-observability
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:
triage_column_id: 18588697
cockroachdb/unowned:
aliases:
cockroachdb/rfc-prs: other
triage_column_id: 0 # TODO
cockroachdb/migrations:
label: T-migrations
triage_column_id: 18330909
cockroachdb/release-eng:
label: T-release
triage_column_id: 9149730