Labels

Indicates a PR has been approved by an approver from all required OWNERS files.

Indicates a cherrypick 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 the PR's author has not signed the CNCF CLA.

Indicates the PR's author has signed the CNCF CLA.

Denotes an issue or PR intended to be handled by the code of conduct committee.

Denotes an issue or PR intended to be handled by the steering committee.

If the contributor has signed the DCO or the CNCF CLA (prior to the move to a DCO).

DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed.

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 OWNERS file in it.

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 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.