Labels

• area/ci
• area/testing
• breaking-change

  Denotes a PR that introduces potentially breaking changes that require user action.
• do-not-merge

  Signal to Mergify to block merging of the PR.
• good first issue

  Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
• help wanted

  Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
• 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/design

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

  Categorizes issue or PR as related to documentation.
• 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/organization

  Categorizes issue or PR as related to organization and governance.
• kind/question

  Further information is requested
• kind/regression

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

  Categorizes issue or PR as a support question.
• kind/technical-debt
• low-hanging-fruit

  Good for newcomers
• 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.
• priority/P0
• priority/P1
• priority/P2
• priority/P3
• priority/Pfuture
• priority/Pmaybe
• ready-to-merge

  Signal to Mergify to merge the PR.