Labels
Labels
94 labels
- Indicates a PR has been approved by an approver from all required OWNERS files.
- Denotes a PR or issue which has been fully backported to all required release branches.
- Denotes a PR or issue that has not been fully backported.
- Indicates a PR has been approved by release managers.
- Indicates a PR has been approved by release managers during code freeze.
- 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.
- Pull requests that update a dependency file
- Indicates that a PR is not yet approved to merge into a release branch.
- Indicates that a PR should not merge because it has not been approved for code freeze yet.
- Indicates that a PR should not merge because it's missing one of the documentation labels.
- 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 a PR lacks a `kind/foo` label and requires one.
- 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 a PR that doesn't need documentation (changes).
- Denotes a PR that has a valid documentation reference.
- Denotes a PR that needs documentation (change) that will be done later.
- 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.
- Categorizes issue or PR as related to adding, removing, or otherwise changing an API