Labels

• approved

  Indicates a PR has been approved by an approver from all required OWNERS files.
• area/api
• area/dependency

  Issues or PRs related to dependency changes
• area/release-eng

  Issues or PRs related to release engineering.
• area/security
• dependencies

  Indicates a PR that update a dependency file.
• kind/api-change

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

  A report or fix for a problem with functional correctness.
• 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.
• kind/documentation

  Categorizes issue or PR as related to documentation.
• kind/failing-test

  Categorizes issue or PR as related to a consistently or frequently failing test.
• kind/feature

  Categorizes issue or PR as related to a new feature.
• kind/flake

  Categorizes issue or PR as related to a flaky test.
• kind/improvement

  A report of a quality problem, or a change that addresses a quality problem.
• kind/regression

  Categorizes issue or PR as related to a regression from a prior release.
• kind/support

  Categorizes issue or PR as a support question.
• 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/lgtm

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

  Denotes an issue or PR has remained open with no activity and has become stale.
• needs/kind

  Indicates that an issue or PR lacks a `kind/foo` label and requires one.
• needs/priority

  Indicates that an issue or PR lacks a `priority/foo` label and requires one.
• needs/rebase

  Indicates a PR cannot be merged because it has merge conflicts with HEAD.
• priority/awaiting-more-evidence

  Lowest priority. Possibly useful, but not yet enough support to actually get it done.
• priority/backlog

  Higher priority than priority/awaiting-more-evidence.
• priority/critical-urgent

  Highest priority. Must be actively worked on as someone's top priority right now.
• priority/important-longterm

  Important over the long term, but may not be staffed and/or may need multiple releases to complete.
• priority/important-soon

  Must be staffed and worked on either currently, or very soon, ideally in time for the next release.