Each label in the repository has a description attached that describes what the label means.
There are 7 label categories in the repository:
- Area labels: These labels denote the general area of the project an issue or PR affects. These start with
A-
. - Category labels: These labels denote the type of issue or change being made, for example
C-bug
An unexpected or incorrect behavior or C-enhancementNew feature or request . These start withC-
. - Difficulty labels: These are reserved for the very easy or very hard issues. Any issue without one of these labels can be considered to be of "average difficulty". They start with
D-
. - Meta labels: These start with
M-
and convey meaning to the core contributors, usually about the release process. - Platform labels: These describe the platform an issue is present on. They start with
O-
. - Priority labels: These are reserved for issues that require more immediate attention (high priority and critical priority) and they start with
P-
. - Status labels: These labels convey meaning to contributors about an issue or PR's status, e.g. whether they are blocked or need triage. They start with
S-
. - EIP/network upgrade labels: These labels are attached to PRs and issues related to specific EIPs or network upgrades. They start with
E-
For easier at-a-glance communication of the status of issues and PRs the following labels are available:
Needs work
-
S-blocked
This cannot more forward until something else changes -
S-needs-benchmark
This set of changes needs performance benchmarking to double-check that they help -
S-needs-design
This issue requires design work to think about how it would best be accomplished -
S-needs-investigation
This issue requires detective work to figure out what's going wrong -
S-needs-rebase
This PR needs to be rebased
Closure reasons
-
S-duplicate
This issue or PR already exists -
S-wontfix
This issue is the result of a deliberate design decision, and will not be fixed
Miscellaneous
-
S-needs-triage
This issue needs to be labelled -
S-controversial
This requires a heightened standard of review before it can be merged