Labels

• action: cleanup

  action: cleanup

  The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews

• action: global presubmit

  action: global presubmit

  The PR is in need of a google3 global presubmit

• action: merge

  action: merge

  The PR is ready for merge by the caretaker

• action: presubmit

  action: presubmit

  The PR is in need of a google3 presubmit

• action: review

  action: review

  The PR is still awaiting reviews from at least one requested reviewer

• area: build & ci

  area: build & ci

  Related the build and CI infrastructure of the project

• area: docs

  area: docs

  Related to the documentation

• area: performance

  area: performance

  Issues related to performance

• bug

  bug

  Something isn't working

• detected: breaking change

  detected: breaking change

  PR contains a commit with a breaking change

• detected: deprecation

  detected: deprecation

  PR contains a commit with a deprecation

• detected: feature

  detected: feature

  PR contains a feature commit

• documentation

  documentation

  Improvements or additions to documentation

• duplicate

  duplicate

  This issue or pull request already exists

• enhancement

  enhancement

  New feature or request

• feature

  feature

  Label used to distinguish feature request from other issues

• gemini-triaged

  gemini-triaged

  Label noting that an issue has been triaged by gemini

• good first issue

  good first issue

  Label noting a good first issue to be worked on by a community member

• help wanted

  help wanted

  Label noting an issue which the team is looking for contribution from the community to fix

• invalid

  invalid

  This doesn't seem right

• merge: caretaker note

  merge: caretaker note

  Alert the caretaker performing the merge to check the PR for an out of normal action needed or note

• merge: preserve commits

  merge: preserve commits

  When the PR is merged, a rebase and merge should be performed

• merge: squash commits

  merge: squash commits

  When the PR is merged, a squash and merge should be performed

• P0

  P0

  Issue that causes an outage, breakage, or major function to be unusable, with no known workarounds

• P1

  P1

  Impacts a large percentage of users; if a workaround exists it is partial or overly painful

• P2

  P2

  The issue is important to a large percentage of users, with a workaround

• P3

  P3

  An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

• P4

  P4

  A relatively minor issue that is not relevant to core functions

• P5

  P5

  The team acknowledges the request but does not plan to address it, it remains open for discussion

• question

  question

  Further information is requested