Indicates a PR has been approved by an approver from all required OWNERS files.
Indicates a PR directly modifies the demos
Indicates a PR directly modifies end to end tests
Indicates a PR directly modifies the proxy code
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager
Indicates that at least one commit in this pull request is missing the DCO sign-off message.
Indicates that all commits in the pull request have the valid DCO sign-off message.
Pull requests that update a dependency file
Indicates that a PR should not merge because it touches files in blocked paths.
Indicates that a PR is not yet approved to merge into a release branch.
Indicates that a PR should not merge because someone has issued a /hold command.
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.
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 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 new feature.
Categorizes issue or PR as related to a flaky test.
Indicates that a PR is ready to be merged.
Indicates that an issue or PR should not be auto-closed due to staleness.
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Denotes an issue or PR has remained open with no activity and has become stale.
Indicates a PR lacks a `kind/foo` label and requires one.
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.