Indicates a PR has been approved by an approver from all required OWNERS files.
Denotes that at least one commit in the pull request doesn't have a valid DCO signoff message.
Denotes that all commits in the pull request have the valid DCO signoff message.
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 OWNERS file in it.
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.
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 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.
Categorizes issue or PR as a question.
Indicates that a PR is ready to be merged.
Indicates that an issue or PR is actively being worked on by a contributor.
Denotes an issue or PR is blocked.
Indicates that an issue or PR should not be auto-closed due to staleness.
Denotes an issue or PR that has aged beyond stale.
Denotes an issue or PR has remained open with no activity and has become stale.
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 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.