Skip to content

Labels

Labels

116 labels

  • needs-ok-to-test

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

  • needs-rebase

    needs-rebase
    Indicates a PR cannot be merged because it has merge conflicts with HEAD.

  • needs-sig

    needs-sig
    Indicates an issue lacks a `sig/foo` label and requires one.

  • ok-to-test

    ok-to-test

  • priority/awaiting-more-evidence

    priority/awaiting-more-evidence
    Lowest priority. Possibly useful, but not yet enough support to actually get it done.

  • priority/backlog

    priority/backlog
    Higher priority than priority/awaiting-more-evidence.

  • priority/critical-urgent

    priority/critical-urgent
    Highest priority. Must be actively worked on as someone's top priority right now.

  • priority/failing-test

    priority/failing-test
    Automatically filed frequently failing test. Needs to be investigated.

  • 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.

  • priority/P0

    priority/P0

  • priority/P1

    priority/P1

  • priority/P2

    priority/P2

  • priority/P3

    priority/P3

  • proposal

    proposal

  • queue/blocks-others

    queue/blocks-others
    DEPRECATED.

  • queue/critical-fix

    queue/critical-fix
    DEPRECATED.

  • queue/fix

    queue/fix
    DEPRECATED.

  • queue/multiple-rebases

    queue/multiple-rebases
    DEPRECATED.

  • 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.

  • release-note-none

    release-note-none
    Denotes a PR that doesn't merit a release note.

  • retest-not-required

    retest-not-required
    Indicates that a PR doesn't need to be retested prior to merge.

  • retest-not-required-docs-only

    retest-not-required-docs-only
    Indicates that a PR doesn't need to be retested prior to merge because it only changes docs.

  • sig/api-machinery

    sig/api-machinery
    Categorizes an issue or PR as relevant to sig-api-machinery.

  • sig/apps

    sig/apps
    Categorizes an issue or PR as relevant to sig-apps.

  • sig/architecture

    sig/architecture
    Categorizes an issue or PR as relevant to sig-architecture.

  • sig/auth

    sig/auth
    Categorizes an issue or PR as relevant to sig-auth.

  • sig/autoscaling

    sig/autoscaling
    Categorizes an issue or PR as relevant to sig-autoscaling.

  • sig/aws

    sig/aws
    Categorizes an issue or PR as relevant to sig-aws.