Labels
Labels
74 labels
- Categorizes an issue or PR as actively needing an API review.
- Indicates a PR has been approved by an approver from all required OWNERS files.
- Issues or PRs related to api-lifecycle changes
- Issues or PRs related to CLI changes
- Issues or PRs related to core changes
- Issues or PRs related to dependency changes
- Issues or PRs related to sharding changes
- Something isn't working
- Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
- Indicates the PR's author has not signed the CNCF CLA.
- Indicates the PR's author has signed the CNCF CLA.
- Indicates the PR's author has not signed the DCO.
- Indicates the PR's author has signed the DCO.
- 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 has an invalid commit message.
- 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.
- Improvements or additions to documentation
- This issue or pull request already exists
- New feature or request
- 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 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.