Skip to content

Labels

Labels

43 labels

  • approved

    approved
    Indicates a PR has been approved by an approver from all required OWNERS files.

  • do-not-merge/hold

    do-not-merge/hold
    Indicates that a PR should not merge because someone has issued a /hold command.

  • do-not-merge/release-note-label-needed

    do-not-merge/release-note-label-needed
    Indicates that a PR should not merge because it's missing one of the release note labels.

  • do-not-merge/work-in-progress

    do-not-merge/work-in-progress
    Indicates that a PR should not merge because it is a work in progress.

  • documentation

    documentation
    Improvements or additions to documentation

  • duplicate

    duplicate
    This issue or pull request already exists

  • enhancement

    enhancement
    New feature or request

  • good first issue

    good first issue
    Good for newcomers

  • help wanted

    help wanted
    Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

  • invalid

    invalid
    This doesn't seem right

  • kind/api-change

    kind/api-change
    Categorizes issue or PR as related to adding, removing, or otherwise changing an API

  • kind/bug

    kind/bug
    Categorizes issue or PR as related to a bug.

  • kind/cleanup

    kind/cleanup
    Categorizes issue or PR as related to cleaning up code, process, or technical debt.

  • kind/design

    kind/design
    Categorizes issue or PR as related to design.

  • kind/documentation

    kind/documentation
    Categorizes issue or PR as related to documentation.

  • kind/enhancement

    kind/enhancement
    Categorizes issue or PR as related to enhancement.

  • kind/feature

    kind/feature
    Categorizes issue or PR as related to a new feature.

  • kind/flake

    kind/flake
    Categorizes issue or PR as related to a flaky test.

  • kind/new-api

    kind/new-api
    Categorizes issue or PR as related to new api.

  • kind/support

    kind/support
    Categorizes issue or PR as related to support.

  • kind/technical-debt

    kind/technical-debt
    Categorizes issue or PR as related to technical debt.

  • kind/upgrade-test-failure

    kind/upgrade-test-failure
    Categorizes issue or PR as related to a consistently or frequently failing test.

  • kind/upstream

    kind/upstream
    Categorizes issue or PR as related to upstream.

  • lgtm

    lgtm
    Indicates that a PR is ready to be merged.

  • lifecycle/frozen

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

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

  • priority/P0

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