Labels

• approved

  approved

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

• breaking

  breaking

  This PR contains a breaking change and should be listed accordingly in release notes.

• bug

  bug

  Something isn't working

• cherry-pick-approved

  cherry-pick-approved

  Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.

• component/prow

  component/prow

  Prow components

• do-not-merge/blocked-paths

  do-not-merge/blocked-paths

  Indicates that a PR should not merge because it touches files in blocked paths.

• do-not-merge/cherry-pick-not-approved

  do-not-merge/cherry-pick-not-approved

  Indicates that a PR is not yet approved to merge into a release branch.

• do-not-merge/contains-merge-commits

  do-not-merge/contains-merge-commits

  Indicates a PR which contains merge commits.

• do-not-merge/hold

  do-not-merge/hold

  Indicates that a PR should not merge because someone has issued a /hold command.

• do-not-merge/invalid-commit-message

  do-not-merge/invalid-commit-message

  Indicates that a PR should not merge because it has an invalid commit message.

• do-not-merge/invalid-owners-file

  do-not-merge/invalid-owners-file

  Indicates that a PR should not merge because it has an invalid OWNERS file in it.

• do-not-merge/needs-kind

  do-not-merge/needs-kind

  Indicates a PR lacks a `kind/foo` label and requires one.

• do-not-merge/release-note-label-needed

  do-not-merge/release-note-label-needed

  Indicates that a PR should not merge because it's missing one of the release note labels.

• do-not-merge/work-in-progress

  do-not-merge/work-in-progress

  Indicates that a PR should not merge because it is a work in progress.

• documentation

  documentation

  Improvements or additions to documentation

• duplicate

  duplicate

  This issue or pull request already exists

• emergency-change

  emergency-change

  Indicates an Emergency change

• enhancement

  enhancement

  New feature or request

• good first issue

  good first issue

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

• help wanted

  help wanted

  Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

• invalid

  invalid

  This doesn't seem right

• kind/api-change

  kind/api-change

  API change with impact on API users

• kind/bug

  kind/bug

  Bug

• kind/cherry-pick

  kind/cherry-pick

  This is a cherry-pick and should be documented as such

• kind/cleanup

  kind/cleanup

  Something that is not needed anymore and can be cleaned up

• kind/discussion

  kind/discussion

  Discussion (engaging others in deciding about multiple options)

• kind/enhancement

  kind/enhancement

  Enhancement, improvement, extension

• kind/epic

  kind/epic

  Large multi-story topic

• kind/flake

  kind/flake

  Tracking or fixing a flaky test

• kind/impediment

  kind/impediment

  Something that impedes developers, operators, users or others in their work