Skip to content

Labels

Labels

  • good first issue

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

    Denotes an issue that needs help from a contributor.
  • 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/documentation

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

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

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

    Indicates an issue or PR lacks a `triage/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/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.
  • triage/accepted

    Indicates an issue or PR is ready to be actively worked on.
  • triage/duplicate

    Indicates an issue is a duplicate of other open issue.
  • triage/needs-information

    Indicates an issue needs more information in order to work on it.
  • triage/not-reproducible

    Indicates an issue can not be reproduced as described.
  • triage/unresolved

    Indicates an issue that can not or will not be resolved.