Labels

• approved

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

  Denotes a PR or issue which has been fully backported to all required release branches.
• backport-needed

  Denotes a PR or issue that has not been fully backported.
• cherry-pick-approved

  Indicates a PR has been approved by release managers.
• code-freeze-approved

  Indicates a PR has been approved by release managers during code freeze.
• dco-signoff: no

  Denotes that at least one commit in the pull request doesn't have a valid DCO signoff message.
• dco-signoff: yes

  Denotes that all commits in the pull request have the valid DCO signoff message.
• dependencies

  Pull requests that update a dependency file
• do-not-merge/cherry-pick-not-approved

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

  Indicates that a PR should not merge because it has not been approved for code freeze yet.
• do-not-merge/docs-needed

  Indicates that a PR should not merge because it's missing one of the documentation labels.
• do-not-merge/hold

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

  Denotes a PR that doesn't need documentation (changes).
• docs/provided

  Denotes a PR that has a valid documentation reference.
• docs/tbd

  Denotes a PR that needs documentation (change) that will be done later.
• documentation

  Improvements or additions to documentation
• duplicate

  This issue or pull request already exists
• 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.
• invalid

  This doesn't seem right
• kind/api-change

  Categorizes issue or PR as related to adding, removing, or otherwise changing an API
• kind/bug

  Categorizes issue or PR as related to a bug.
• kind/chore

  Updating grunt tasks etc; no production code changes.
• kind/cleanup

  Categorizes issue or PR as related to cleaning up code, process, or technical debt.
• kind/deprecation

  Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
• kind/design

  Categorizes issue or PR as related to design.