Skip to content

Labels

Labels

  • approved

    Indicates a PR has been approved by an approver from all required OWNERS files.
  • good first issue

    Denotes an issue ready for a new contributor.
  • help wanted

    Denotes an issue that needs help from a contributor.
  • kind/automation

    Categorizes issue or PR as related to CI/CD or an automation.
  • 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/config

    Categorizes issue or PR as related to a new configuration.
  • kind/documentation

    Categorizes issue or PR as related to documentation.
  • kind/feature

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

    Categorizes issue or PR as that fixes some issue.
  • kind/monitoring

    Categorizes issue or PR as related to monitoring.
  • kind/release

    Categorizes issue or PR as related to a new release.
  • lgtm

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

    Indicates that an issue or PR should not be auto-closed due to staleness.
  • needs-env

    Indicates a PR or issue lacks a `env/foo` label and requires one.
  • needs-kind

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

    Indicates a PR or issue lacks a `priority/foo` label and requires one.
  • needs-size

    Indicates a PR or issue lacks a `size/foo` label and requires one.
  • 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/blocked

    Currently blocked by another task, issue or PR.
  • 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 sprints to complete.
  • priority/important-soon

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

    Categorizes issue as a support question.
  • size/L

    Requires few days to complete the PR or the issue.
  • size/M

    Requires about a day to complete the PR or the issue.
  • size/S

    Requires less than a day to complete the PR or the issue.
  • size/XL

    Requires about a week to complete the PR or the issue.
  • size/XS

    Requires less than an hour to complete the PR or the issue.