You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/contributing-code/repo-labels/contents.lr
+52-42
Original file line number
Diff line number
Diff line change
@@ -4,13 +4,16 @@ _template: page-with-toc.html
4
4
---
5
5
title: Repository Labels
6
6
---
7
-
description: To facilitate the community in finding ways to contribute that match their experiences and skillsets, we have developed a comprehensive system for labelling issues and PRs. This is an introduction to this standard labelling scheme.
7
+
description: To facilitate the community in finding ways to contribute that
8
+
match their experiences and skillsets, we have developed a comprehensive system
9
+
for labelling issues and PRs. This is an introduction to this standard
10
+
labelling scheme.
8
11
---
9
12
body:
10
13
11
-
Labels consist of three fields, viz. name, description and color. Label names
12
-
should have a consistent format to aid both filtering within the github UI as
13
-
well as scanning visually through the list. The following format is the most
14
+
Labels consist of three fields, viz. name, description and color. Label names
15
+
should have a consistent format to aid both filtering within the github UI as
16
+
well as scanning visually through the list. The following format is the most
14
17
suited to this task (where `β΅` denotes a single space):
15
18
16
19
```
@@ -31,6 +34,7 @@ An issue has many different attributes:
31
34
- Talk
32
35
- Friendliness
33
36
37
+
34
38
### *Priority
35
39
36
40
<divclass="table-container">
@@ -59,8 +63,8 @@ An issue has many different attributes:
59
63
</table>
60
64
</div>
61
65
62
-
The priority of an issue is based on its impact, derived from a combination of
63
-
urgency and importance. This determines the importance of the issue when sprint
66
+
The priority of an issue is based on its impact, derived from a combination of
67
+
urgency and importance. This determines the importance of the issue when sprint
64
68
planning or deciding which issues to tackle next.
65
69
66
70
- <spanclass="gh-label priority-unfavourable">
@@ -80,6 +84,7 @@ planning or deciding which issues to tackle next.
80
84
</span>
81
85
-**Description:** Low priority and doesn't need to be rushed
82
86
87
+
83
88
### *Status
84
89
85
90
<divclass="table-container">
@@ -112,32 +117,24 @@ The status of the issue determines whether it is ready for work or not. Issues
112
117
may not be ready to be worked on for a number of reasons and the maintainers
113
118
must keep updating the labels as the situation evolves.
114
119
115
-
An issue, at the time of closing can have either the
120
+
An issue, at the time of closing can have either the
116
121
<spanclass="gh-label status-light">
117
122
π status: ready for dev
118
123
</span>
119
-
or the
124
+
or the
120
125
<spanclass="gh-label status-lighter">
121
126
βοΈ status: discarded
122
127
</span>
123
128
label based on whether it was closed with or without resolution, respectively.
124
129
125
-
- <spanclass="gh-label status-light">
126
-
π status: ready for dev
130
+
- <spanclass="gh-label status-darker">
131
+
π¦ status: awaiting triage
127
132
</span>
128
-
-**Description:**Ready for work
133
+
-**Description:**Has not been triaged & therefore, not ready for work
129
134
- <spanclass="gh-label status-neutral">
130
135
π§ status: blocked
131
136
</span>
132
137
-**Description:** Blocked & therefore, not ready for work
133
-
- <spanclass="gh-label status-dark">
134
-
π§Ή status: ticket work required
135
-
</span>
136
-
-**Description:** Needs more details before it can be worked on
137
-
- <spanclass="gh-label status-dark">
138
-
π· status: label work required
139
-
</span>
140
-
-**Description:** Needs proper labelling before it can be worked on
141
138
- <spanclass="gh-label status-lighter">
142
139
βοΈ status: discarded
143
140
</span>
@@ -146,10 +143,19 @@ label based on whether it was closed with or without resolution, respectively.
146
143
π status: discontinued
147
144
</span>
148
145
-**Description:** Not suitable for work as repo is in maintenance
149
-
- <spanclass="gh-label status-darker">
150
-
π¦ status: awaiting triage
146
+
- <spanclass="gh-label status-dark">
147
+
π· status: label work required
151
148
</span>
152
-
-**Description:** Has not been triaged & therefore, not ready for work
149
+
-**Description:** Needs proper labelling before it can be worked on
150
+
- <spanclass="gh-label status-light">
151
+
π status: ready for dev
152
+
</span>
153
+
-**Description:** Ready for work
154
+
- <spanclass="gh-label status-dark">
155
+
π§Ή status: ticket work required
156
+
</span>
157
+
-**Description:** Needs more details before it can be worked on
158
+
153
159
154
160
### *Goal
155
161
@@ -158,54 +164,60 @@ represents the impact of the issue on the scope of the software.
0 commit comments