Labels

• approved

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

  This PR contains a breaking change and should be listed accordingly in release notes.
• cherry-pick-approved

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

  Prow components
• 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

  Indicates that a PR is not yet approved to merge into a release branch.
• do-not-merge/contains-merge-commits

  Indicates a PR which contains merge commits.
• do-not-merge/hold

  Indicates that a PR should not merge because someone has issued a /hold command.
• 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

  Indicates that a PR should not merge because it has an invalid OWNERS file in it.
• do-not-merge/needs-kind

  Indicates a PR lacks a `kind/foo` label and requires one.
• 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

  Indicates that a PR should not merge because it is a work in progress.
• good first issue

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

  Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
• kind/api-change

  API change with impact on API users
• kind/bug

  Bug
• kind/cherry-pick

  This is a cherry-pick and should be documented as such
• kind/cleanup

  Something that is not needed anymore and can be cleaned up
• kind/discussion

  Discussion (engaging others in deciding about multiple options)
• kind/enhancement

  Enhancement, improvement, extension
• kind/epic

  Large multi-story topic
• kind/flake

  Tracking or fixing a flaky test
• kind/impediment

  Something that impedes developers, operators, users or others in their work
• kind/poc

  Proof of concept or prototype
• kind/post-mortem

  Bug that requires deeper analysis after immediate issues were resolved (usually after downtime)
• kind/question

  Question (asking for help, advice, or technical detail)
• kind/regression

  Bug that hit us already in the past and that is reappearing/requires a proper solution
• kind/task

  General task
• kind/technical-debt

  Something that is only solved on the surface, but requires more (re)work to be done properly