Labels

• approved

  approved

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

• area/arm64

  area/arm64

  Categorizes issue or PR as related to arm64.

• area/deploy

  area/deploy

  Categorizes issue or PR as related to deploy.

• area/testing

  area/testing

  Categorizes issue or PR as related to testing.

• bug

  bug

• dco-signoff: no

  dco-signoff: no

• dco-signoff: yes

  dco-signoff: yes

• dependencies

  dependencies

  Pull requests that update a dependency file

• do-not-merge/hold

  do-not-merge/hold

• 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.

• duplicate

  duplicate

• 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

• kind/api-change

  kind/api-change

  Categorizes issue or PR as related to adding, removing, or otherwise changing an API

• kind/bug

  kind/bug

  Categorizes issue or PR as related to a bug.

• kind/cleanup

  kind/cleanup

  Categorizes issue or PR as related to cleaning up code, process, or technical debt.

• kind/design

  kind/design

  Categorizes issue or PR as related to design.

• kind/documentation

  kind/documentation

  Categorizes issue or PR as related to documentation.

• kind/failing-test

  kind/failing-test

  Categorizes issue or PR as related to a consistently or frequently failing test.

• kind/feature

  kind/feature

  Categorizes issue or PR as related to a new feature.

• kind/flake

  kind/flake

  Categorizes issue or PR as related to a flaky test.

• kind/proposal

  kind/proposal

  Categorizes issue as related to a proposal.

• kind/support

  kind/support

  Categorizes issue as related to a support request.

• lgtm

  lgtm

  Indicates that a PR is ready to be merged.

• priority/awaiting-more-evidence

  priority/awaiting-more-evidence

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

• priority/backlog

  priority/backlog

  Higher priority than priority/awaiting-more-evidence.

• priority/critical-urgent

  priority/critical-urgent

  Highest priority. Must be actively worked on as someone's top priority right now.

• priority/important-longterm

  priority/important-longterm

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

• priority/important-soon

  priority/important-soon

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