@@ -7,7 +7,7 @@ scheduling into milestones. Labelling is a task for everyone.
7
7
Most issues will have labels for at least one of the following:
8
8
9
9
- Type: ~ feature, ~ bug, ~ customer, etc.
10
- - Subject: ~ wiki, ~ "container registry ", ~ ldap, ~ api, ~ frontend, etc.
10
+ - Subject: ~ wiki, ~ "Container Registry ", ~ ldap, ~ api, ~ frontend, etc.
11
11
- Team: ~ Plan, ~ Manage, ~ Quality, etc.
12
12
- Stage: ~ "devops: plan ", ~ "devops: create ", etc.
13
13
- Release Scoping: ~ Deliverable, ~ Stretch, ~ "Next Patch Release"
@@ -44,7 +44,7 @@ Subject labels are labels that define what area or feature of GitLab this issue
44
44
hits. They are not always necessary, but very convenient.
45
45
46
46
Examples of subject labels are ~ wiki, ~ ldap, ~ api,
47
- ~ issues, ~ "merge requests", ~ labels, and ~ "container registry ".
47
+ ~ issues, ~ "merge requests", ~ labels, and ~ "Container Registry ".
48
48
49
49
If you are an expert in a particular area, it makes it easier to find issues to
50
50
work on. You can also subscribe to those labels to receive an email each time an
0 commit comments