Skip to content

Labels

Labels

  • approved

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

    Relates to backend
  • area/frontend

    Relates to frontend
  • area/infra

    Relates to infrastructure
  • area/metrics

    Relates to metrics
  • area/reliability

    Relates to reliability
  • area/security

    Relates to security
  • area/ux

    Relates to user experience
  • blocked

    Indicates that this is blocked. Link the blocker
  • dependencies

    Pull requests that update a dependency file
  • do-not-merge/blocked-paths

    Indicates that a PR should not merge because it touches files in blocked paths.
  • 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/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
  • Feature

  • help wanted

    Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
  • Improvement

  • Internal

  • kind/bug

    Categorizes issue or PR as related to a bug.
  • 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/epic

    An epic is a large body of work that can be broken down into a number of smaller Issues.
  • 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/incident-followup

    Categorizes issue or PR as related to an incident report.