Labels

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

Edge deployment related

New feature or request

Epic tracking issue

Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.

Pull requests that update GitHub Actions code

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.

Initialization related

This doesn't seem right

Question about whether this issue is still valid

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 a feature/enhancement marked for deprecation.

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.