Indicates a PR that requires an org member to verify it is safe to test.
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
Indicates an issue or PR lacks a `sig/foo` label and requires one.
Indicates an issue or PR lacks a `triage/foo` label and requires one.
Indicates a non-member PR verified by an org member that is safe to test.
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Higher priority than priority/awaiting-more-evidence.
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 releases to complete.
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Denotes a PR that will be considered when it comes time to generate release notes.
Denotes a PR that introduces potentially breaking changes that require user action.
Denotes a PR that doesn't merit a release note.
Categorizes an issue or PR as relevant to SIG API Machinery.
Categorizes an issue or PR as relevant to SIG Apps.
Categorizes an issue or PR as relevant to SIG Architecture.
Categorizes an issue or PR as relevant to SIG Auth.
Categorizes an issue or PR as relevant to SIG Autoscaling.
Categorizes an issue or PR as relevant to SIG CLI.
Categorizes an issue or PR as relevant to SIG Cloud Provider.
Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.