Indicates a PR has been approved by an approver from all required OWNERS files.
Denotes an issue ready for a new contributor.
Denotes an issue that needs help from a contributor.
Categorizes issue or PR as related to CI/CD or an automation.
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 documentation.
Categorizes issue or PR as related to a new feature.
Categorizes issue or PR as related to monitoring.
Indicates that a PR is ready to be merged.
Indicates that an issue or PR should not be auto-closed due to staleness.
Indicates a PR or issue lacks a `env/foo` label and requires one.
Indicates a PR or issue lacks a `kind/foo` label and requires one.
Indicates a PR or issue lacks a `priority/foo` label and requires one.
Indicates a PR or issue lacks a `size/foo` label and requires one.
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Higher priority than priority/awaiting-more-evidence.
Currently blocked by another task, issue or PR.
Highest priority. Must be actively worked on as someone's top priority right now.
Important over the long term, but may not be staffed and/or may need multiple sprints to complete.
Must be staffed and worked on either currently, or very soon, ideally in time for the next sprint.
Categorizes issue as a support question.
Requires few days to complete the PR or the issue.
Requires about a day to complete the PR or the issue.
Requires less than a day to complete the PR or the issue.
Requires about a week to complete the PR or the issue.
Requires less than an hour to complete the PR or the issue.
Requires more than a week to complete the PR or the issue.