Labels

• lgtm

  Indicates that a PR is ready to be merged.
• lifecycle/active

  Indicates that an issue or PR is actively being worked on by a contributor.
• lifecycle/frozen

  Indicates that an issue or PR should not be auto-closed due to staleness.
• lifecycle/rotten

  Denotes an issue or PR that has aged beyond stale and will be auto-closed.
• lifecycle/stale

  Denotes an issue or PR has remained open with no activity and has become stale.
• needs-approver-review

  Indicates that a PR requires a review from an approver.
• needs-ok-to-test

  Indicates a PR that requires an org member to verify it is safe to test.
• needs-rebase

  Indicates a PR cannot be merged because it has merge conflicts with HEAD.
• ok-to-test

  Indicates a non-member PR verified by an org member that is safe to test.
• priority/backlog

  Indicate that the issue or PR is a lower priority and can be worked on in the future
• priority/critical-urgent

  Categorizes an issue or pull request as critical and of urgent priority.
• question

  Further information is requested
• release-note

  Denotes a PR that will be considered when it comes time to generate release notes.
• release-note-action-required

  Denotes a PR that introduces potentially breaking changes that require user action.
• release-note-none

  Denotes a PR that doesn't merit a release note.
• sig/api

  Denotes an issue or PR that relates to changes in api.
• sig/buildsystem

  Denotes an issue or PR that relates to changes in the build system.
• sig/ci

  Denotes an issue or PR as being related to sig-ci, marks changes to the CI system.
• sig/compute
• sig/documentation
• sig/network
• sig/observability

  Denotes an issue or PR that relates to observability.
• sig/release
• sig/scale
• sig/security
• sig/storage
• sig/testing
• size/L
• size/M
• size/S