Labels

• approved

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

  Something isn't working
• dco-signoff: no

  Indicates the PR's author has not DCO signed all their commits.
• dco-signoff: yes

  Indicates the PR's author has DCO signed all their commits.
• do-not-merge/hold

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

  This issue or pull request already exists
• enhancement

  New feature or request
• good-first-issue
• hacktoberfest

  Categorizes as a Hacktoberfest contribution
• help wanted

  Extra attention is needed
• invalid

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

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

  Indicates the PR/issue deprecates a feature that will be removed in a subsequent release.
• kind/enhancement
• kind/flake

  Categorizes issue or PR as related to a flaky test.
• kind/proposal
• kind/question
• kind/tracker
• lgtm

  Indicates that a PR is ready to be merged.
• lifecycle/active

  Indicates that an issue or PR is actively being worked on by a contributor.
• lifecycle/frozen

  Indicates that an issue or PR should not be auto-closed due to staleness.
• lifecycle/rotten

  Denotes an issue or PR that has aged beyond stale and will be auto-closed.
• lifecycle/stale

  Denotes an issue or PR has remained open with no activity and has become stale.
• needs-ok-to-test

  Indicates a PR that requires an org member to verify it is safe to test.
• needs-rebase

  Indicates a PR cannot be merged because it has merge conflicts with HEAD.