Skip to content

Labels

Labels

95 labels

  • lifecycle/rotten

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

  • lifecycle/stale

    lifecycle/stale
    Denotes an issue or PR has remained open with no activity and has become stale.

  • needs-kind

    needs-kind
    Indicates a PR lacks a `kind/foo` label and requires one.

  • 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 or PR lacks a `sig/foo` label and requires one.

  • needs-triage

    needs-triage
    Indicates an issue or PR lacks a `triage/foo` label and requires one.

  • ok-to-test

    ok-to-test
    Indicates a non-member PR verified by an org member that is safe 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/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.

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

  • size/L

    size/L
    Denotes a PR that changes 100-499 lines, ignoring generated files.

  • size/M

    size/M
    Denotes a PR that changes 30-99 lines, ignoring generated files.

  • size/S

    size/S
    Denotes a PR that changes 10-29 lines, ignoring generated files.

  • size/XL

    size/XL
    Denotes a PR that changes 500-999 lines, ignoring generated files.

  • size/XS

    size/XS
    Denotes a PR that changes 0-9 lines, ignoring generated files.

  • size/XXL

    size/XXL
    Denotes a PR that changes 1000+ lines, ignoring generated files.

  • staff-eng-approved

    staff-eng-approved
    Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead).

  • tide/merge-blocker

    tide/merge-blocker
    Denotes an issue that blocks the tide merge queue for a branch while it is open.

  • tide/merge-method-merge

    tide/merge-method-merge
    Denotes a PR that should use a standard merge by tide when it merges.

  • tide/merge-method-rebase

    tide/merge-method-rebase
    Denotes a PR that should be rebased by tide when it merges.

  • tide/merge-method-squash

    tide/merge-method-squash
    Denotes a PR that should be squashed by tide when it merges.

  • triage/accepted

    triage/accepted
    Indicates an issue or PR is ready to be actively worked on.

  • triage/duplicate

    triage/duplicate
    Indicates an issue is a duplicate of other open issue.

  • triage/needs-information

    triage/needs-information
    Indicates an issue needs more information in order to work on it.