Labels

• 1: PM Review

  1: PM Review

  Requires review by a product manager

• 1: UX Review

  1: UX Review

  Requires review by ux

• 2: Dev Review

  2: Dev Review

  Requires review by a developer

• 2: Infra Review

  2: Infra Review

  Requires review by a SRE

• 3: QA Review

  3: QA Review

  Requires review by a QA engineer

• 3: Security Review

  3: Security Review

  Review requested from Security Team

• 4: Reviews Complete

  4: Reviews Complete

  All reviewers have approved the pull request

• do-not-merge

  do-not-merge

  Should not be merged until this label is removed

• do-not-merge/awaiting-PR

  do-not-merge/awaiting-PR

• do-not-merge/awaiting-submitter-action

  do-not-merge/awaiting-submitter-action

  Blocked on the author

• do-not-merge/release-note-label-needed

  do-not-merge/release-note-label-needed

• do-not-merge/work-in-progress

  do-not-merge/work-in-progress

• hacktoberfest-accepted

  hacktoberfest-accepted

• kind/api-change

  kind/api-change

  Categorizes issue or PR as related to adding, removing, or otherwise changing an API

• kind/bug

  kind/bug

  Categorizes issue or PR as related to a bug.

• kind/chore

  kind/chore

  Categorizes issue or PR as related to updates that are not production code.

• kind/cleanup

  kind/cleanup

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

• kind/deprecation

  kind/deprecation

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

• kind/design

  kind/design

  Categorizes issue or PR as related to design.

• kind/documentation

  kind/documentation

  Categorizes issue or PR as related to documentation.

• kind/feature

  kind/feature

  Categorizes issue or PR as related to a new feature.

• kind/regression

  kind/regression

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

• Lifecycle/1:stale

  Lifecycle/1:stale

• Lifecycle/frozen

  Lifecycle/frozen

• priority/critical-urgent

  priority/critical-urgent

  Highest priority. Must be actively worked on as someone's top priority right now.

• priority/important-longterm

  priority/important-longterm

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

• priority/important-soon

  priority/important-soon

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

• QA/Tests Not Required

  QA/Tests Not Required

• release-note

  release-note

  Denotes a PR that will be considered when it comes time to generate release notes.

• release-note-action-required

  release-note-action-required

  Denotes a PR that introduces potentially breaking changes that require user action.