Repository navigation
Expand file tree
/
Copy pathprow.yaml
More file actions
141 lines (130 loc) · 5.55 KB
/
Copy pathprow.yaml
File metadata and controls
141 lines (130 loc) · 5.55 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
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
# Starter organization-wide prow configuration.
# Put it at <org>/.github/prow.yaml (or in a private <org>/.project, read with a token that can
# see it); every repository of the organization inherits it and may layer its own
# .github/prow.yaml on top. Reference: docs/configuration.md.
#
# Every key under `labels` is a /<key> command; run the label-sync job once so the labels exist.
# label-sync also creates the built-in lgtm, approved, do-not-merge/hold, help wanted,
# good first issue and ok-to-test labels. Colors follow kubernetes/test-infra's label_sync.
labels:
kind:
- name: bug
color: e11d21
description: Categorizes issue or PR as related to a bug.
- name: cleanup
color: c5def5
description: Categorizes issue or PR as related to cleaning up code, process, or technical debt.
- name: documentation
color: c7def8
description: Categorizes issue or PR as related to documentation.
- name: feature
color: c7def8
description: Categorizes issue or PR as related to a new feature.
- name: failing-test
color: e11d21
description: Categorizes issue or PR as related to a consistently or frequently failing test.
- name: regression
color: e11d21
description: Categorizes issue or PR as related to a regression from a prior release.
# exclusive: a later /priority replaces the existing priority/* label
priority:
values:
- name: critical-urgent
color: e11d21
description: Highest priority. Must be actively worked on as someone's top priority right now.
- name: important-soon
color: eb6420
description: Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
- name: important-longterm
color: eb6420
description: Important over the long term, but may not be staffed and/or may need multiple releases to complete.
- name: backlog
color: fbca04
description: Higher priority than priority/awaiting-more-evidence.
- name: awaiting-more-evidence
color: fef2c0
description: Lowest priority. Possibly useful, but not yet enough support to actually get it done.
exclusive: true
triage:
values:
- name: accepted
color: 8fc951
description: Indicates an issue or PR is ready to be actively worked on.
- name: needs-information
color: d455d0
description: Indicates an issue needs more information in order to work on it.
- name: duplicate
color: d455d0
description: Indicates an issue is a duplicate of other open issue.
- name: not-reproducible
color: d455d0
description: Indicates an issue can not be reproduced as described.
exclusive: true
# the built-in /lifecycle values, spelled out so their labels are created too
lifecycle:
values:
- name: frozen
color: d3e2f0
description: Indicates that an issue or PR should not be auto-closed due to staleness.
- name: stale
color: '795548'
description: Denotes an issue or PR has remained open with no activity and has become stale.
- name: rotten
color: '604460'
description: Denotes an issue or PR that has aged beyond stale and will be auto-closed.
exclusive: true
# the merge gate's deny list; /hold applies do-not-merge/hold
do-not-merge:
- name: hold
color: e11d21
description: Indicates that a PR should not merge because someone has issued a /hold command.
- name: work-in-progress
color: e11d21
description: Indicates that a PR should not merge because it is a work in progress.
- name: invalid-owners-file
color: e11d21
description: Indicates that a PR should not merge because it has an invalid OWNERS file in it.
# needs-* labels until a matching label is applied; needs-* labels are colored ededed
require_matching_label:
- regexp: ^kind/
missing_label: needs-kind
issues: true
prs: true
missing_comment: Please add a kind label with /kind <value>.
- regexp: ^triage/
missing_label: needs-triage
issues: true
prs: false
# the merge gate; these are the defaults
tide:
labels: [lgtm]
missing_labels: [do-not-merge/*, needs-rebase, hold]
merge_method: merge
merge_on_events: true
merge_queue: auto # enqueue into a required GitHub merge queue instead of merging; off: always merge directly
# the label /hold applies; this is the default
hold:
label: do-not-merge/hold
# reviewers requested from OWNERS files when a pull request opens
blunderbuss:
request_count: 2
ignore_drafts: true
ignore_authors: ['dependabot[bot]']
# /lgtm records the reviewed commit as a prow/lgtm commit status and merges only while the head
# still carries it (needs statuses: write); this is the default
lgtm:
bind_to_commit: true
# the sweep job (pull_request install mode) evaluates the pull requests updated within this
# window; this is the default
sweep:
lookback: 1h
# who may run the label commands, /hold, /close and the review commands; these are the defaults.
# users is unioned with the organization's list; review only applies without OWNERS files.
# Do not add an OWNERS file just to grant triage: it changes who may /lgtm and /approve and the
# merge gate. See docs/configuration.md#authorization.
# authorization:
# labels: anyone # anyone, collaborators, members or trusted
# hold: anyone
# close: collaborators # the issue or PR author may always /close
# review: members # members or trusted
# users: [] # extra trusted logins, case-insensitive