Issue Labeling

Purpose

This documents goal is to explain the process used to label issues.

Categories of Labels

Category	Description
Area	Marks an area of expertise within the code base, i.e. A-graphql or A-grpc
Bug	Classification of a bug and its impact, i.e. B-crash or B-regression. Use B-bug for generic catchall
Category	Classification of the issue opened, i.e. C-feature-request or C-improvement
Candidate	Identify an issue as best handled in a plugin or as available in a beta release, i.e. CA-beta or CA-plugin
Dependency	Indicates that a given issue is related to a specific dependency, i.e. D-electron or D-node-libcurl
Experience	Surfaces what experience level with the code base is needed to fix a given issue, i.e. E-good-first-issue
Feature Phase	Indicates the depth of a given feature and how it is expected to enter the app, i.e. FP-alpha or FP-ga
Marked	Provides a fast glance look as to why a given issue was closed, i.e. M-as-intended or M-duplicate
Needs	Indicates that a given issue is blocked in some capacity with a specific need, i.e. N-investigation or N-author-input
Operating Systems	Indicates that a given issue impacts specific OSs only, i.e. O-linux-snap or O-windows
Priority	How soon we expect to address a given issue based on impact, i.e. P-critical or P-low
Package	Tags an issue as being relevant to one of Insomnia's internal packages, i.e. PA-importers
Status	Current status of a given issue or pull request, i.e. S-blocked or s-unverified

One Off Labels

Category	Description
dependencies	Used by Dependabot
hacktoberfest-accepted	Attached to pull requests related to Hacktoberfest
PR-wip	Apply if your pull request is not ready for full review
stale	Used by Stale Bot