Skip to content

No labels!

There aren’t any labels for this repository quite yet.

59 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
approved
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
cherry-pick-approved
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager
dco-signoff: no
dco-signoff: no
Indicates that at least one commit in this pull request is missing the DCO sign-off message.
1
dco-signoff: yes
dco-signoff: yes
Indicates that all commits in the pull request have the valid DCO sign-off message.
1
dependencies
dependencies
Pull requests that update a dependency file
1
do-not-merge/blocked-paths
do-not-merge/blocked-paths
Indicates that a PR should not merge because it touches files in blocked paths.
do-not-merge/cherry-pick-not-approved
do-not-merge/cherry-pick-not-approved
Indicates that a PR is not yet approved to merge into a release branch.
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/invalid-owners-file
do-not-merge/invalid-owners-file
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
go
go
Pull requests that update Go code
1
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
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/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/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.
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-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.
2
needs-rebase
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.