Categorizes issue or PR as related to a bug
Categorizes issue or PR as related to cleaning up code, process, or technical debt
Categorizes issue or PR as related to a feature/enhancement marked for deprecation
Categorizes issue or PR as related to a discussion
Categorizes issue or PR as related to documentation
Categorizes issue or PR as related to a new feature
Categorizes issue or PR as related to a question
Categorizes issue or PR as related to Renovate
Categorizes issue or PR as a support question
Indicates that an issue or PR is actively being worked on by a contributor.
Indicates that an issue or PR should not be auto-closed due to staleness.
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Denotes an issue or PR has remained open with no activity and has become stale.
Indicates an issue or PR lacks a `area/foo` label and requires one.
Indicates a PR lacks a `kind/foo` label and requires one.
Indicates a PR lacks a `lifecycle/foo` label and requires one.
Indicates a PR lacks a `priority/foo` label and requires one.
Indicates an issue or PR lacks a `size/foo` label and requires one.
Indicates an issue or PR lacks a `status/foo` label and requires one.
Indicates an issue or PR lacks a `triage/foo` label and requires one.
Possibly useful, but not yet enough support to actually get it done
Highest priority. This should be dealt with ASAP
After critical issues are fixed, these should be dealt with before any further issues
This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix
This issue or PR may be useful, and needs some attention