Labels

• breaking
• bug

  Categorizes issue or PR as related to a bug.
• ci/skip-e2e

  E2E tests will be skipped for this PR
• ci/skip-load-test

  Load tests will be skipped for this PR
• cleanup

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

  Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
• design

  Categorizes issue or PR as related to design.
• do-not-merge
• documentation

  Categorizes issue or PR as related to documentation.
• Epic
• feature request

  Categorizes issue or PR as related to a new feature or enhancement.
• good first issue

  Good for newcomers
• priority/backlog

  Generalistic priority.
• priority/critical

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

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

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

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

  Categorizes issue or PR as a support question.
• sustain

  Categorizes issue or PR as related to sustainability.
• test

  Categorizes issue or PR as related to a consistently or frequently failing test.
• triage/accepted

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

  Indicates an issue that can not or will not be resolved.
• triage/duplicate

  Indicates an issue is a duplicate of other open issue.
• triage/in-progress

  Issue or PR is in the process of being triaged.
• 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/pending

  Issue or PR is pending for triage and prioritization.