As a project grows, issue/PR labels can play an increasingly important role in managing a large nubmer of issues/PRs. This document has some guidelines that can improve consistency across projects and help make the use of labels more productive.
Unless mentioned otherwise, labels are applied to issues only (not PRs).
While GitHub does not have the concept of label groups, we can simulate label groups using systematic label naming. i.e. labels having the same prefix are considered part of a label group.
There are two types of label groups:
Common label groups:
p.Critical: Would like to fix it ASAP and release as a hot patch.
p.Urgent: Would like to handle in the very next release.
p.High: Enhances user experience significantly, would like to do in the next few releases.
p.Medium: Marginal impact on user experience.
p.Low: Very little impact, unlikely to do in the near future.
p.Zero: Unlikely to do, ever.
NOTE: An issue is considered as accepted when a priority label has been assigned.
s.OnHold: The work on the issue has been put on hold pending some other event.
s.ToReview: Waiting for the review.
s.Ongoing: The PR is being worked on.
s.ToMerge: Main reviewer approved the changes.
s.MergeApproved: Both main reviewer and the code quality reviewer has approved the merge. PR can be merged.
s.OnHold: The work on the PR has been put on hold pending some other event.
c.Enhancement: An enhancement to an existing functionality (not big enough to be considered as a user story).
c.Story: A user story.
c.Feature: A new feature.
c.Theme: A feature that be broken down into many user-stories/features.
c.Chore: Other work items such as updating documentation.
c.Message: Issue used as a means of discussing something with the dev team.
d.Easy: For new contributors to do as their first PR. MUST be simple enough to be contained in one commit.
d.Moderate: Moderate difficulty. Small localized change.
d.VeryHard: More difficult issues that are better left for committers or more senior developers.
This label can be used to indicate how much effort is expected for (or was spent on) an issue.
e.1 is roughly equal to an hour of work,
e.2 is two hours of work, and so on. Recommended values: 1,2,4,8,16,32
Effort labels can be applied to PRs indicate effort for reviewing (by the main reviewer). Those applied for issues can indicate the effort for fixing the issue.
Classifies the issues based on the non-functional aspect it tackles. Some examples:
| ||Controlling access to user groups, authentication, privacy, anonymity|
| ||Refactorings that are mainly to improve code/design quality|
| ||Things related to concurrent access, session control|
| ||CI, release management, version control, dev docs|
| ||User docs, product website|
| ||Resilience to user errors, environmental problems|
| ||Speed of operation|
| ||Saving data permanently|
| ||Related to behavior at increasing loads|
| ||Protection from security threats|
| ||Testing efficiency and robustness (as opposed to testing a specific feature)|
| ||User interface, User experience, Responsiveness|
Classifies the issue based on the feature it involves. These labels depend on the project.
Classifies the issue based on the tool/technology it involves. Some examples given below.
| ||CSS, Bootstrap|
| ||HTML, Browsers|
| ||JSTL, JSP, Servlets|
good first issue: for first time contributors (note that GitHub treats this label in a special way)
kudos: to appreciate good work done in a PR