Skip to content

No labels!

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

204 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
committee/code-of-conduct
committee/code-of-conduct
Denotes an issue or PR intended to be handled by the code of conduct committee.
committee/security-response
committee/security-response
Denotes an issue or PR intended to be handled by the product security committee.
9
committee/steering
committee/steering
Denotes an issue or PR intended to be handled by the steering committee.
dependencies
dependencies
Pull requests that update a dependency file
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.
35
do-not-merge/contains-merge-commits
do-not-merge/contains-merge-commits
Indicates a PR which contains merge commits.
9
do-not-merge/hold
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
92
do-not-merge/invalid-commit-message
do-not-merge/invalid-commit-message
Indicates that a PR should not merge because it has an invalid commit message.
do-not-merge/invalid-owners-file
do-not-merge/invalid-owners-file
Indicates that a PR should not merge because it has an invalid OWNERS file in it.
do-not-merge/needs-kind
do-not-merge/needs-kind
Indicates a PR lacks a `kind/foo` label and requires one.
65
do-not-merge/needs-sig
do-not-merge/needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
4
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.
102
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.
105
do-not-merge
do-not-merge
DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed.
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
17
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
131
kind/api-change
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
105
kind/bug
kind/bug
Categorizes issue or PR as related to a bug.
997
kind/cleanup
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
349
kind/deprecation
kind/deprecation
Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
5
kind/design
kind/design
Categorizes issue or PR as related to design.
1
kind/documentation
kind/documentation
Categorizes issue or PR as related to documentation.
77
kind/failing-test
kind/failing-test
Categorizes issue or PR as related to a consistently or frequently failing test.
46
kind/feature
kind/feature
Categorizes issue or PR as related to a new feature.
820
kind/flake
kind/flake
Categorizes issue or PR as related to a flaky test.
65
kind/regression
kind/regression
Categorizes issue or PR as related to a regression from a prior release.
14
kind/support
kind/support
Categorizes issue or PR as a support question.
18
lgtm
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
111
lifecycle/active
lifecycle/active
Indicates that an issue or PR is actively being worked on by a contributor.
1