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 lacks a `sig/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.
Highest priority. Must be actively worked on as someone's top priority right now.
Automatically filed frequently failing test. Needs to be investigated.
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.
Indicates that a PR doesn't need to be retested prior to merge.
Indicates that a PR doesn't need to be retested prior to merge because it only changes docs.
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-aws.