Indicates a PR has been approved by an approver from all required OWNERS files.
Indicates the PR's author has not signed the CNCF CLA.
Indicates the PR's author has signed the CNCF CLA.
Indicates a PR which contains merge commits.
Indicates that a PR should not merge because someone has issued a /hold command.
Indicates that a PR should not merge because it has an invalid commit message.
Indicates that a PR should not merge because it's missing one of the release note labels.
Indicates that a PR should not merge because it is a work in progress.
Improvements or additions to documentation
This issue or pull request already exists
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
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 design.
Categorizes issue or PR as related to documentation.
Categorizes issue or PR as related to a consistently or frequently failing test.
Categorizes issue or PR as related to a new feature.
Categorizes issue or PR as related to a flaky test.
Indicates an issue that is a support question.
Indicates that a PR is ready to be merged.
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.
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
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.