Labels

• automerge

  automerge

  Merge the pull request once unit tests and other checks pass.

• automerge: exact

  automerge: exact

  Summon MOG for automerging, but approvals need to be against the latest commit

• autorelease: pending

  autorelease: pending

  Release please needs to do its work on this.

• autorelease: tagged

  autorelease: tagged

  Release please has completed a release for this.

• autorelease: triggered

  autorelease: triggered

  Release please has triggered a release for this.

• blunderbuss: assign

  blunderbuss: assign

  Instruct blunderbuss to assign someone

• do not merge

  do not merge

  Indicates a pull request not ready for merge, due to either quality or timing.

• duplicate

  duplicate

• flakybot: flaky

  flakybot: flaky

  Tells the Flaky Bot not to close or comment on this issue.

• flakybot: issue

  flakybot: issue

  An issue filed by the Flaky Bot. Should not be added manually.

• flakybot: quiet

  flakybot: quiet

  Instruct flakybot to be silent

• priority: p0

  priority: p0

  Highest priority. Critical issue. P0 implies highest priority.

• priority: p1

  priority: p1

  Important issue which blocks shipping the next release. Will be fixed prior to next release.

• priority: p2

  priority: p2

  Moderately-important priority. Fix may not be included in next release.

• priority: p3

  priority: p3

  Desirable enhancement or fix. May not be included in next release.

• type: bug

  type: bug

  Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

• type: cleanup

  type: cleanup

  An internal cleanup or hygiene concern.

• type: docs

  type: docs

  Improvement to the documentation for an API.

• type: feature request

  type: feature request

  ‘Nice-to-have’ improvement, new feature or different behavior or design.

• type: process

  type: process

  A process-related concern. May include testing, release, or the like.

• type: question

  type: question

  Request for information or clarification.