Labels
Labels
71 labels
- Indicates a PR has been approved by an approver from all required OWNERS files.
- Indicates a PR related to cert-manager
- Indicates a PR related to cert-manager-csi
- Indicates a PR related to flightdeck
- Indicates a PR related to istio-csr
- Indicates a PR related to kube-oidc-proxy
- Indicates a PR related to okta-kubectl-auth
- Indicates a PR related to prow
- Indicates a PR related to tarmak
- Indicates a PR related to terraform-google-gke-cluster
- Indicates a PR related to testing
- Indicates a cherry-pick PR into a release branch has been approved by the release branch manager
- Denotes a PR to master as a candidate for cherry picking into a release branch.
- 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
- Pull requests that update go code
- 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.
- This doesn't seem right
- Categorizes issue or PR as related to a bug.
- Indicates a PR that is an automated image bump
- Categorizes issue or PR as related to cleaning up code, process, or technical debt.